public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41198] gfortran 4.5 does not produce "Warning: Deleted feature: GOTO at (1) jumps to END of construct at (2)"
Date: Mon, 31 Aug 2009 15:43:00 -0000 [thread overview]
Message-ID: <20090831154315.32143.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41198-14284@http.gcc.gnu.org/bugzilla/>
------- 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
> GOTO 50
> 50 ENDIF
> END PROGRAM test
>
I believe that 4.3 and 4.4 had a bug. Gfortran 4.5 is doing the right
thing. The deleted feature is
(2) Branching to an END IF statement from outside its block.
In Fortran 77, and for consistency also in Fortran 90, it was
possible to branch to an END IF statement from outside the IF
construct; this has been deleted. A similar result can be
achieved by branching to a CONTINUE statement that is immediately
after the END IF statement.
Your GOTO 50 is inside the its block. I also believe that there was
a long thread in fortran@gcc about this (non)feature. I'll see if
I can find it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41198
next prev parent reply other threads:[~2009-08-31 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 14:26 [Bug fortran/41198] New: " michael dot a dot richmond at nasa dot gov
2009-08-31 15:43 ` kargl at gcc dot gnu dot org [this message]
2009-08-31 18:01 ` [Bug fortran/41198] " michael dot a dot richmond at nasa dot gov
2009-08-31 18:42 ` mikael at gcc dot gnu dot org
2009-08-31 18:58 ` kargl at gcc dot gnu dot org
2009-12-04 23:38 ` dfranke at gcc dot gnu dot org
2010-01-16 23:25 ` kargl at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090831154315.32143.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).