[Bug libgomp/109904] linking with -static flag generates undefined references

2023-05-18 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109904 --- Comment #8 from GARY.WHITE at ColoState dot edu --- So send me the link where I should get the binaries from. Gary C. White, CWB(r) Professor Emeritus Department of Fish, Wildlife, and Conservation Biology 10 Wagar Colorado State Universit

[Bug libgomp/109904] linking with -static flag generates undefined references

2023-05-18 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109904 --- Comment #6 from GARY.WHITE at ColoState dot edu --- So using -ldl seems really quirky. Doesn't seem to work for generating 32-bit executables. Plus, not working at all on my second machine. Is there a better solution? Gary C. White, CWB

[Bug libgomp/109904] linking with -static flag generates undefined references

2023-05-18 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109904 --- Comment #5 from GARY.WHITE at ColoState dot edu --- I'm getting gfortran downloads from here: https://github.com/brechtsanders/winlibs_mingw/releases Gary C. White, CWB(r) Professor Emeritus Department of Fish, Wildlife, and Conservation

[Bug libgomp/109904] linking with -static flag generates undefined references

2023-05-18 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109904 --- Comment #3 from GARY.WHITE at ColoState dot edu --- Linking with -ldl fixed the issue Where is there documentation of -ldl? Gary C. White, CWB(r) Professor Emeritus Department of Fish, Wildlife, and Conservation Biology 10 Wagar Colorado

[Bug fortran/109904] New: linking with -static flag generates undefined references

2023-05-18 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109904 Bug ID: 109904 Summary: linking with -static flag generates undefined references Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Pr

[Bug fortran/109865] different results when routine moved inside the contains statement

2023-05-17 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865 GARY.WHITE at ColoState dot edu changed: What|Removed |Added Resolution|--- |FIXED Sta

[Bug fortran/109865] different results when routine moved inside the contains statement

2023-05-16 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865 --- Comment #14 from GARY.WHITE at ColoState dot edu --- Clarification on the last post. I'm compiling everything with -O3, except va09ad.f90. If va09ad.f90 is compiled with -O3, you get the bug. If va09ad.f90 is compiled with -O0, the code p

[Bug fortran/109865] different results when routine moved inside the contains statement

2023-05-16 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865 --- Comment #12 from GARY.WHITE at ColoState dot edu --- I just checked, and the bug occurs with the LAPACK routines instead of LinPack. So "make type=markLAPACK" will generate markLAPACK that will fail with -O3, but work with -O0. --- Comment

[Bug fortran/109865] different results when routine moved inside the contains statement

2023-05-16 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865 --- Comment #12 from GARY.WHITE at ColoState dot edu --- I just checked, and the bug occurs with the LAPACK routines instead of LinPack. So "make type=markLAPACK" will generate markLAPACK that will fail with -O3, but work with -O0. --- Comment

[Bug fortran/109865] different results when routine moved inside the contains statement

2023-05-16 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865 --- Comment #11 from GARY.WHITE at ColoState dot edu --- I've never used valgrind -- what would it do? The problem isn't that the code is wrong -- otherwise -O0 would not generate correct results. The compiler is optimizing something incorrect

[Bug fortran/109865] different results when routine moved inside the contains statement

2023-05-16 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865 --- Comment #9 from GARY.WHITE at ColoState dot edu --- Another clue. I'm seeing the same bug in gfortran-13, except that I have to use -O0 for both cases of mc11ad.f90 in or out of the contains statement. Similarly, if I put the set of va09a

[Bug fortran/109865] different results when routine moved inside the contains statement

2023-05-15 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865 --- Comment #8 from GARY.WHITE at ColoState dot edu --- I just tried to send you a zip file with all the code and instructions (see below), but it is over 6Mb in size, and was rejected. Where can I put it that you can access it? I have put the

[Bug fortran/109865] different results when routine moved inside the contains statement

2023-05-15 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865 --- Comment #7 from 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 w

[Bug fortran/109865] different results when routine moved inside the contains statement

2023-05-15 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865 --- Comment #5 from GARY.WHITE at ColoState dot edu --- (In reply to Steve Kargl from comment #4) > On Mon, May 15, 2023 at 07:11:17PM +, Gary.White at ColoState dot edu > wrote: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865 > > (I

[Bug fortran/109865] different results when routine moved inside the contains statement

2023-05-15 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865 --- Comment #3 from GARY.WHITE at ColoState dot edu --- (In reply to kargl from comment #2) > (In reply to gary.wh...@colostate.edu from comment #0) > > Created attachment 55087 [details] > > set of subroutines where moving mc11ad inside the con

[Bug fortran/109865] New: different results when routine moved inside the contains statement

2023-05-15 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865 Bug ID: 109865 Summary: different results when routine moved inside the contains statement Product: gcc Version: og12 (devel/omp/gcc-12) Status: UNCONFIRMED Se

[Bug libfortran/106509] executable hangs if -static is included in compile

2022-08-23 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106509 --- Comment #4 from GARY.WHITE at ColoState dot edu --- Somewhat resolved -- does not happen with UCRT, only with MSVCRT.

[Bug libfortran/106509] executable hangs if -static is included in compile

2022-08-02 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106509 --- Comment #2 from GARY.WHITE at ColoState dot edu --- (In reply to Andrew Pinski from comment #1) > -static and glibc and pthreads (which openmp uses) has always been > problematic. Why do you want to use -static? Because I'm distributing a l

[Bug fortran/106509] New: executable hangs if -static is included in compile

2022-08-02 Thread Gary.White at ColoState dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106509 Bug ID: 106509 Summary: executable hangs if -static is included in compile Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Compon