https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865
--- Comment #7 from GARY.WHITE at ColoState dot edu <Gary.White at ColoState dot edu> --- Sorry I can't simplify this down to a nice compact piece of code, but ... In the attached test_case.zip file are all the *.f90 files, makefile, and some library files that work on ubuntu with gfortran-12. I can provide Windows libraries if that is easier. Create the executable file, mark64, by a simple make or make type=mark64 Right now, the makefile does not have an -O0 on the va09ad.f90 compile line. As we found out, over-riding -O3 on va09ad.f90 compilation produces correct code. Execute the test case with ./mark64 i=dipper.inp o=dipper.out I've included 2 output files, dipper_correct.out and dipper_incorrect.out so you can see what correct and incorrect outputs look like. Hopefully this all works out. Thanks. Gary Gary C. White, CWB(r) Professor Emeritus Department of Fish, Wildlife, and Conservation Biology 10 Wagar Colorado State University Fort Collins, CO 80523 (515)450-2768 Mobile gary.wh...@colostate.edu https://sites.warnercnr.colostate.edu/gwhite/ he/him/his See where we are! "Leadership is a privilege to better the lives of others. It is not an opportunity to satisfy personal greed." Mwai Kibaki -----Original Message----- From: kargl at gcc dot gnu.org <gcc-bugzi...@gcc.gnu.org> Sent: Monday, May 15, 2023 2:42 PM To: White,Gary <gary.wh...@colostate.edu> Subject: [Bug fortran/109865] different results when routine moved inside the contains statement ** Caution: EXTERNAL Sender ** https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865 --- Comment #6 from kargl at gcc dot gnu.org --- (In reply to gary.wh...@colostate.edu from comment #5) > (In reply to Steve Kargl from comment #4) > > I assume you've also tried with -fcheck=all. > > Your report states you're using og12. If it supports the sanitizer, > > can you add -fsanitize=undefined to the options? > > -fcheck=all does not generate any warnings. > -fsanitize=undefined returns pages when loading of: > > undefined reference to `__ubsan_handle_pointer_overflow' > > which makes no sense to me???? Hmmm. Thanks for checking. Either your version of gcc is not built with --enable-libsanitizer or gfortran cannot find the library. At this point, it seems we're going to need a complete testcase. -- You are receiving this mail because: You reported the bug.
