https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50525
--- Comment #6 from Vittorio Zecca ---
Still in trunk.
The NAG nagfor and Intel ifort compilers detect the issue.
ifort -S -w gfbug72.f
gfbug72.f(4): error #6482: An ENTRY dummy argument is referenced in an
executable statement before it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50525
--- Comment #5 from Dominique d'Humieres ---
Duplicate of pr34663?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50525
Dominique d'Humieres dominiq at lps dot ens.fr changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50525
Tobias Burnus burnus at gcc dot gnu.org changed:
What|Removed |Added
Keywords||accepts-invalid
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50525
--- Comment #2 from Tobias Burnus burnus at gcc dot gnu.org 2011-09-27
12:12:03 UTC ---
I meant something like the following. Though, the wording could be improved.
--- a/gcc/fortran/decl.c
+++ b/gcc/fortran/decl.c
@@ -4296,6 +4296,14 @@
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50525
--- Comment #3 from Tobias Burnus burnus at gcc dot gnu.org 2011-09-27
14:27:39 UTC ---
The patch causes regressions as it comes before the check in resolve_variable
(search for before the ENTRY, which covers a similar issue (cf PR 25090).
