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] PR34137 ENTRY fixes: allow in modules, fix diagnostics

From: Jerry DeLisle <jvdelisle at verizon dot net>
To: Tobias Burnus <burnus at net-b dot de>
Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>, "'fortran at gcc dot gnu dot org'" <fortran at gcc dot gnu dot org>
Date: Sun, 18 Nov 2007 07:38:12 -0800
Subject: Re: [Patch, Fortran] PR34137 ENTRY fixes: allow in modules, fix diagnostics
References: <474021BC.7050601@net-b.de>

Tobias Burnus wrote:

:ADDPATCH fortran:

Hi all,

when trying to fix PR34079 (incl. ENTRY), I encountered first that
BIND(C) does not work for ENTRY and, secondly, some deficits in the
Fortran 95 support of ENTRY.

a) ENTRY was rejected in a module as the master function had no type.

Entry may not be used as internal procedure, but it is allowed as module
procedure. Or in words of the standard (F95/F2003):

Constraint: An entry-stmt may appear only in an external-subprogram or
module-subprogram. An entry-stmt shall not appear within an
executable-construct.

C1253 (R1235) An entry-stmt shall appear only in an external-subprogram
or module-subprogram. An entry-stmt shall not appear within an
executable-construct.


b) It was possible to assign to the ENTRY name, even if a RESULT was
specified. This lead to an ICE later on.

Build and regression tested on x86-64. OK for the trunk?

Tobias

OK, thanks!

Jerry

References:
- [Patch, Fortran] PR34137 ENTRY fixes: allow in modules, fix diagnostics
  - From: Tobias Burnus

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