https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84922
--- Comment #12 from William Clodius <w.clodius at icloud dot com> --- FWIW I was told on comp.lang.fortran that the code is erroneous because of "The error message doesn't make much sense to me, but I think Note 12.2 in section 12.4.3.1 contains a clue to what's going on. It states: " "An interface body cannot be used to describe the interface of an internal procedure, a module procedure that is not a separate module procedure, or an intrinsic procedure because the interfaces of such procedures are already explicit.” Still the wording of the original error message suggests that there is an inconsistency in the matching process. > On Mar 21, 2018, at 2:24 PM, sgk at troutmask dot apl.washington.edu > <gcc-bugzi...@gcc.gnu.org> wrote: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84922 > > --- Comment #8 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- > On Wed, Mar 21, 2018 at 08:11:29PM +0000, w.clodius at icloud dot com wrote: >> --- Comment #6 from William Clodius <w.clodius at icloud dot com> --- >> My version of gfortran, 7.1, doesn’t give the first message, which is >> correct. >> The second message is incorrect. Either the clashing procedures should not be >> compared further, or the comparison of the shapes of the arguments should >> find >> that they match. > > Of course, 7.1 does give the first message, as I just fixed > the issue. But, I need to pull out a copy of the Standard > to make sure the patch is correct. > > One still gets the second error message as gfortran runs > a sequence of matchers in parse the code. She issues > all errors that she finds, where some are run-on errors. > Fix the first and others go away. > > -- > You are receiving this mail because: > You reported the bug.
