This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch, fortran] Fix PR 91390 - treatment of extra parameter in a subroutine call

From: Thomas König <tk at tkoenig dot net>
To: sgk at troutmask dot apl dot washington dot edu
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>
Date: Sat, 24 Aug 2019 23:15:10 +0200
Subject: Re: [patch, fortran] Fix PR 91390 - treatment of extra parameter in a subroutine call
References: <81d346ae-3da0-d082-234d-a0cc64050a7e@tkoenig.net> <20190824171837.GA24268@troutmask.apl.washington.edu>

Hi Steve,

OK.  Thanks for taking on this task.


Committed (r274902). Thanks for the review!

As to the open question about how to handle this check,
I would create -fallow-argument-mismatch (or whatever
option name you like).  gfortran issues an error if
a mismatch is detected.  -fallow-... would reduce the
error to warning, which can only be silenced with -w.
Hopefully, this will encourage users to fix the code.


Yes, that is what I will submit next.  -fallow-argument-mismatch
sounds like a good name, unless somebody else comes up with a
better name.

Regards

	Thomas

References:
- [patch, fortran] Fix PR 91390 - treatment of extra parameter in a subroutine call
  - From: Thomas König
- Re: [patch, fortran] Fix PR 91390 - treatment of extra parameter in a subroutine call
  - From: Steve Kargl

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]