This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [gfortran, committed] PR 24008: require argument list for function entries
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Tobias dot Schlueter at Physik dot Uni-Muenchen dot DE
- Cc: fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Tue, 1 Nov 2005 17:31:09 -0500
- Subject: Re: [gfortran, committed] PR 24008: require argument list for function entries
- References: <1130882133.4367e455c7b7c@www.cip.physik.uni-muenchen.de>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Tue, Nov 01, 2005 at 10:55:33PM +0100, Tobias.Schlueter@Physik.Uni-Muenchen.DE wrote:
>
> This trivial one-liner fixes a small bug in the parsing of function entries,
> where we would allow entry declarations of the form
> ENTRY f RESULT(a)
> This is in fact not allowed, but an empty argument list is required. (Actually,
> in fixed form this would be parsed as ENTRY fresult(a), so there is a reason why
> the argument list is required.)
Are you sure about that? 4 months ago you said you don't see such a
requirement in the standard:
http://gcc.gnu.org/ml/fortran/2005-07/msg00051.html
It is clear that ENTRY foo RESULT (bar) should be disallowed, but
ENTRY foo
in FUNCTION IMHO shouldn't.
> Patch together with new testcase below. I also had to fix an old test.
> Bubblestrapped and tested. Committed to the mainline as r106358.
Jakub