public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/56284] [OOP] ICE with alternate return in type-bound procedure Date: Tue, 12 Feb 2013 12:58:00 -0000 [thread overview] Message-ID: <bug-56284-4-LkD6dB4qzO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56284-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56284 --- Comment #9 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2013-02-12 12:57:55 UTC --- Do you understand why the test in gfc_match_return (file match.c) if (gfc_notify_std (GFC_STD_F95_OBS, "Alternate RETURN " "at %C") == FAILURE) return MATCH_ERROR; is not used? Note that the error is slightly different to the one used in comment #5. Otherwise the patches fix this PR without regression. Thanks.
next prev parent reply other threads:[~2013-02-12 12:58 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-11 8:58 [Bug fortran/56284] New: ICE with contained routine which inappropriately compares a string and a number arjen.markus at deltares dot nl 2013-02-11 9:02 ` [Bug fortran/56284] " arjen.markus at deltares dot nl 2013-02-11 9:51 ` [Bug fortran/56284] [OOP] " janus at gcc dot gnu.org 2013-02-11 10:09 ` [Bug fortran/56284] [OOP] ICE with alternate return in type-bound procedure janus at gcc dot gnu.org 2013-02-11 12:17 ` janus at gcc dot gnu.org 2013-02-11 12:37 ` janus at gcc dot gnu.org 2013-02-11 13:57 ` janus at gcc dot gnu.org 2013-02-11 19:06 ` dominiq at lps dot ens.fr 2013-02-11 19:46 ` janus at gcc dot gnu.org 2013-02-12 12:58 ` dominiq at lps dot ens.fr [this message] 2013-02-12 13:31 ` janus at gcc dot gnu.org 2013-04-03 7:51 ` janus at gcc dot gnu.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=bug-56284-4-LkD6dB4qzO@http.gcc.gnu.org/bugzilla/ \ --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).