[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 sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96033 --- Comment #9 from Steve Kargl --- On Thu, Jul 02, 2020 at 06:30:40PM +, sgk at troutmask dot apl.washington.edu wrote: > > It isn't a matter of simply switching rules. It's a matter of bugs > and whether the bug is reported. In the

[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 sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96033 --- Comment #8 from Steve Kargl --- On Thu, Jul 02, 2020 at 05:31:21PM +, skorzennik at cfa dot harvard.edu wrote: > > I gave up on gfortran when the 64b record marker made it unusable for me. I'm > not surprised it was fixed, but this

[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

[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 sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96033 --- Comment #6 from Steve Kargl --- On Thu, Jul 02, 2020 at 04:10:38PM +, skorzennik at cfa dot harvard.edu wrote: > > GCC is the single one that decides that old code is trash and needs to be > rewritten. When 64b was introduced,

[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

[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 kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96033 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org ---

[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 dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96033 --- Comment #3 from Dominique d'Humieres --- You can find a quite long discussion about legacy at https://groups.google.com/forum/#!topic/comp.lang.fortran/Ed8Mccy9zo8

[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

[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 dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96033 Dominique d'Humieres changed: What|Removed |Added Resolution|--- |INVALID