[Bug fortran/96033] New: error: The Fortran compiler gfortran will not compile files that call the same routine with arguments of different types.

2020-07-02 Thread skorzennik at cfa dot harvard.edu
Version: 10.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: skorzennik at cfa dot harvard.edu Target Milestone: --- Failed to configure to build mvapich2-2.3.[14

[Bug fortran/96033] error: The Fortran compiler gfortran will not compile files that call the same routine with arguments of different types.

2020-07-02 Thread skorzennik at cfa dot harvard.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96033 --- Comment #2 from Sylvain Korzennik --- Merci Dominique. Will transmit info to MVAPICH2 ppl. The configuration script needs to be changed, this is not "faulty code", it is a test code part of the package configuration specifically to test i

[Bug fortran/96033] error: The Fortran compiler gfortran will not compile files that call the same routine with arguments of different types.

2020-07-02 Thread skorzennik at cfa dot harvard.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96033 --- Comment #5 from Sylvain Korzennik --- Hi Kargl, I am not interested in a protracted religious discussion, I simply do not use gfortran for my work (research), but need to provides it form my users (Smithsonian HPC cluster) as part of my du

[Bug fortran/96033] error: The Fortran compiler gfortran will not compile files that call the same routine with arguments of different types.

2020-07-02 Thread skorzennik at cfa dot harvard.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96033 --- Comment #7 from Sylvain Korzennik --- Thanks for following up, Steve. I gave up on gfortran when the 64b record marker made it unusable for me. I'm not surprised it was fixed, but this pointed to poor decision making and ignoring the need to

[Bug c++/92514] New: limits:1668:7: internal compiler error: Illegal instruction

2019-11-14 Thread skorzennik at cfa dot harvard.edu
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: skorzennik at cfa dot harvard.edu Target Milestone: --- Created attachment 47266 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47266&action=edit .ii and .log files In file i

[Bug c++/92514] limits:1668:7: internal compiler error: Illegal instruction

2019-11-14 Thread skorzennik at cfa dot harvard.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92514 --- Comment #2 from Sylvain Korzennik --- ==> gcc-9.2.0/do-configure.sou <== module load gcc/8.2.0 ./configure --prefix=/share/apps/tools/gcc/9.2.0 \ --enable-shared \ --disable-multilib \ --enable-threads=posi

[Bug c++/92514] limits:1668:7: internal compiler error: Illegal instruction

2019-11-14 Thread skorzennik at cfa dot harvard.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92514 --- Comment #3 from Sylvain Korzennik --- => gcc-9.2.0/do-configure.sou <== module load gcc/8.2.0 ./configure --prefix=/share/apps/tools/gcc/9.2.0 \ --enable-shared \ --disable-multilib \ --enable-threads=posix

[Bug c++/92514] limits:1668:7: internal compiler error: Illegal instruction

2019-11-14 Thread skorzennik at cfa dot harvard.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92514 --- Comment #5 from Sylvain Korzennik --- Thanks for your prompt replies! 1- we use a NSF mounted disk to serve ~90 servers (~4100 cores), w/ a set of diff CPUs. It does compile fine on the server the code was built on. 2- what flags do I use t

[Bug c++/92514] limits:1668:7: internal compiler error: Illegal instruction

2019-11-14 Thread skorzennik at cfa dot harvard.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92514 --- Comment #6 from Sylvain Korzennik --- Thanks for your prompt replies! 1- we use a NSF mounted disk to serve ~90 servers (~4100 cores), w/ a set of diff CPUs. It does compile fine on the server the code was built on. 2- what flags do I use t

[Bug c++/92514] limits:1668:7: internal compiler error: Illegal instruction

2019-11-14 Thread skorzennik at cfa dot harvard.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92514 --- Comment #9 from Sylvain Korzennik --- 1- that page does not tell me how to build a generic version ./config.guess returns the same value on ea machine, as does gcc -dumpmachine x86_64-pc-linux-gnu do I add --build=XX --host-XX or --target

[Bug c++/92514] limits:1668:7: internal compiler error: Illegal instruction

2019-11-14 Thread skorzennik at cfa dot harvard.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92514 --- Comment #11 from Sylvain Korzennik --- Thx - for GMP, /config.guess returns skylake-pc-linux-gnu not x86_64-pc-linux-gnu hence the mess... I'll try rebuilding it w/ ./configure --host=x86_64-pc-linux-gnu Cheers, Sylvain -- On Thu