https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50555
--- Comment #7 from Jerry DeLisle ---
Author: jvdelisle
Date: Sun Feb 7 20:15:55 2016
New Revision: 233203
URL: https://gcc.gnu.org/viewcvs?rev=233203=gcc=rev
Log:
2016-02-07 Jerry DeLisle
PR fortran/50555
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50555
Jerry DeLisle changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50555
--- Comment #8 from Jerry DeLisle ---
Closing, fixed on trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50555
--- Comment #6 from Jerry DeLisle ---
This patch:
diff --git a/gcc/fortran/resolve.c b/gcc/fortran/resolve.c
index 64d59cee..8a465db6 100644
--- a/gcc/fortran/resolve.c
+++ b/gcc/fortran/resolve.c
@@ -14275,6 +14275,13 @@ resolve_symbol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50555
--- Comment #3 from Dominique d'Humieres ---
> I found it fixed in 5.2.0 and maybe already in 4.8.2
Are you sure of that? I am expecting an error for the test in comment 0, but I
get none with trunk (6.0), 5.2, and 4.8:
[Book15] f90/bug% gfc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50555
Dominique d'Humieres changed:
What|Removed |Added
Status|RESOLVED|NEW
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50555
--- Comment #4 from Vittorio Zecca ---
Sorry, you are right, the compiler should emit an error message
instead it wrongly
accepts the code. I was confused, this time the right behaviour is to
emit an error message.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50555
Vittorio Zecca changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50555
Dominique d'Humieres dominiq at lps dot ens.fr changed:
What|Removed |Added
Status|UNCONFIRMED |NEW