public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/40881] [F03] warn for obsolescent features Date: Thu, 04 Apr 2013 19:23:00 -0000 [thread overview] Message-ID: <bug-40881-4-H3LX2I5Vph@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-40881-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40881 --- Comment #11 from janus at gcc dot gnu.org 2013-04-04 19:23:26 UTC --- http://gcc.gnu.org/viewcvs/gcc?view=revision&revision=197495 2013-04-04 Janus Weil <janus@gcc.gnu.org> PR fortran/40881 * match.c (gfc_match_return): Remove standard notification. * primary.c (gfc_match_actual_arglist): Add standard notification. 2013-04-04 Janus Weil <janus@gcc.gnu.org> PR fortran/40881 * gfortran.dg/altreturn_1.f90: Add -std=gnu. * gfortran.dg/altreturn_4.f90: Ditto. * gfortran.dg/altreturn_3.f90: Replace -std=legacy by -std=gnu. * gfortran.dg/altreturn_5.f90: Ditto. * gfortran.dg/altreturn_6.f90: Ditto. * gfortran.dg/altreturn_7.f90: Ditto.
next prev parent reply other threads:[~2013-04-04 19:23 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-40881-4@http.gcc.gnu.org/bugzilla/> 2012-08-14 10:26 ` [Bug fortran/40881] " burnus at gcc dot gnu.org 2012-08-14 10:30 ` burnus at gcc dot gnu.org 2013-04-03 7:53 ` [Bug fortran/40881] [F03] " janus at gcc dot gnu.org 2013-04-04 19:23 ` janus at gcc dot gnu.org [this message] 2013-04-04 19:28 ` janus at gcc dot gnu.org 2015-09-08 9:41 ` dominiq at lps dot ens.fr 2015-10-10 9:10 ` dominiq at lps dot ens.fr
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-40881-4-H3LX2I5Vph@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).