------- Comment #1 from fxcoudert at gcc dot gnu dot org 2005-11-26 19:27
-------
Neither gfortran, nor g95, nor Portland see this error.
## gfortran ##
## g95 ##
## Intel ##
fortcom: Error: foo.f90, line 5: An ENTRY dummy argument is referenced in an
executable statement before it appears in any ENTRY statement. [K]
RE1=K
-----^
compilation aborted for foo.f90 (code 1)
## Portland ##
## Sun ##
MODULE M1
^
"foo.f90", Line = 1, Column = 8: ERROR: The compiler has detected errors in
module "M1". No module information file will be created for this module.
FUNCTION F1(I) RESULT(RF1)
^
"foo.f90", Line = 3, Column = 23: WARNING: The result of function name "RF1" in
the function subprogram is not defined.
ENTRY E1(K) RESULT(RE1)
^
"foo.f90", Line = 7, Column = 11: ERROR: Object "K" has been previously used in
an executable statement, therefore it must not be a dummy argument.
^
"foo.f90", Line = 7, Column = 21: ERROR: "RE1" has been used as a variable,
therefore it must not be declared as a result-name.
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Keywords| |accepts-invalid
Last reconfirmed|0000-00-00 00:00:00 |2005-11-26 19:27:28
date| |
Summary|better diagnostic needed |missing diagnostic about
| |ENTRY dummy argument
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25058
