https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91731
--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- On Wed, Sep 11, 2019 at 10:36:20PM +0000, damian at sourceryinstitute dot org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91731 > > --- Comment #3 from Damian Rouson <damian at sourceryinstitute dot org> --- > So do I need to report this to the MPICH developers or is a gfortran bug? I > tried "-w -fallow-argument-mismatch" and got the same error message. > With mpich-3.3.1, I do % setenv PATH ~/work/x/bin:$PATH # set path to find gfortran 10 % setenv FFLAGS "-w -fallow-argument-mismatch -O2" % ./configure |& tee sgk.log % grep mismatched sgk.log checking whether gfortran allows mismatched arguments... yes checking whether gfortran allows mismatched arguments... yes % make -j5 % grep mismatch src/env/* src/env/mpif77.bash:final_fflags=" -w -fallow-argument-mismatch -O2" src/env/mpif77.sh:final_fflags=" -w -fallow-argument-mismatch -O2" works for me. I suppose that someone should file a bug report with MPICH developers to alert them to gfortran's ability to detect argument mismatches in 10.0.0 (aka 10.1 when released). They should be able to 1) fix configure to detect 10 or newer versions to add the appropriate options; and 2) fix their broken code. PS: Frankly, I'm shocked to see that mpich defaults to only F77 in 2019.
