--- Comment #6 from kargl at gcc dot gnu dot org 2010-01-16 23:25 ---
The (non?)issue was fixed on trunk in March 2009. Since this
issues concerns only a warning and generating wrong code is
not possible, I'm closing this with WONTFIX under the 'too many
bugs too fix, too few hands to d
--- Comment #5 from dfranke at gcc dot gnu dot org 2009-12-04 23:37 ---
PR38507 is closed, no backport to 4.4 seems to be planned.
Shouldn't this PR be closed as INVALID?
--
dfranke at gcc dot gnu dot org changed:
What|Removed |Added
--
--- Comment #4 from kargl at gcc dot gnu dot org 2009-08-31 18:58 ---
(In reply to comment #2)
> If I move "GOTO 50" outside of the block, gfortran 4.5 correctly gives the
> message "Warning: Label at (1) is not in the same block as the GOTO statement
> at (2)", but gfortran 4.3 and 4.4
--- Comment #3 from mikael at gcc dot gnu dot org 2009-08-31 18:41 ---
(In reply to comment #1)
> I believe that 4.3 and 4.4 had a bug.
bug #38507 probably
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41198
--- Comment #2 from michael dot a dot richmond at nasa dot gov 2009-08-31
18:00 ---
If I move "GOTO 50" outside of the block, gfortran 4.5 correctly gives the
message "Warning: Label at (1) is not in the same block as the GOTO statement
at (2)", but gfortran 4.3 and 4.4 give no message.
--- Comment #1 from kargl at gcc dot gnu dot org 2009-08-31 15:43 ---
(In reply to comment #0)
> The following program produces a warning message in gfortran 4.3 and 4.4, but
> not 4.5. I believe it produced a warning message in early versions of 4.5.
>
> PROGRAM test
> IF(.TRUE.) THEN
