This is the mail archive of the
mailing list for the GCC project.
What to do with argument mismatches in Fortran (was: [patch, fortran] Fix PR 91443)
- From: Thomas Koenig <tkoenig at netcologne dot de>
- To: Janne Blomqvist <blomqvist dot janne at gmail dot com>
- Cc: "fortran at gcc dot gnu dot org" <fortran at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>, gcc at gcc dot gnu dot org
- Date: Tue, 20 Aug 2019 21:56:27 +0200
- Subject: What to do with argument mismatches in Fortran (was: [patch, fortran] Fix PR 91443)
- References: <email@example.com> <CAO9iq9Fj_uwF1ZCsmFOKNcaFK60SX4gfqdZp7XYh1WXQN+Amkw@mail.gmail.com> <firstname.lastname@example.org>
Committed as r274551.
Well, this revision appears to have woken quite a few bugs from their
slumber. While argument mismatch was always illegal, it seems to have
been a common idiom at one time. And, like almost all bad habits of
the past, SPEC also has this (see PR 91473, where you can see thatt a
rather large number of SPEC tests now require -std=legacy).
So, what to do? Is -std=legacy the right option, or should we add
something different (like -faccept-argument-mismatch), which we
could then set by -std=legacy? And is there anything special
we should be doing after we have diagnoses the problem, if the
user simply wants to run the code?