public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "michael dot a dot richmond at nasa dot gov" <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 18:01:00 -0000 [thread overview] Message-ID: <20090831180058.21722.qmail@sourceware.org> (raw) In-Reply-To: <bug-41198-14284@http.gcc.gnu.org/bugzilla/> ------- 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. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41198
next prev parent reply other threads:[~2009-08-31 18:01 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 ` [Bug fortran/41198] " kargl at gcc dot gnu dot org 2009-08-31 18:01 ` michael dot a dot richmond at nasa dot gov [this message] 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=20090831180058.21722.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: linkBe 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).