https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96033
--- Comment #2 from Sylvain Korzennik <skorzennik at cfa dot harvard.edu> --- 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 if the "Fortran compiler gfortran will compile files that call the same routine with arguments of different types". I ran the configurator ok by setting env vars FFLAGS and FCFLAGS to -std=legacy - hopefully it will build fine. These kind of changes make GCC harder and harder to use/maintain in a professional setting, IM(H)O. Backward compatibility of gfortran is dismal (legacy code that builds fine w/ plethora of other fortran compiler fails to build w/ gfortran - ppl were writing fortran code for quite a wile, like one big scientific package started 60+ years ago, yet gfortran is the one that can't handle it - ifort and pgfortran do fine, it was written/developed on a VAX/VMS back when - author have long retired - desn't make the code obsolete, tho). A bien entendeur.
