public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/34547] [4.8/4.9 regression] NULL(): Fortran 2003 changes, accepts invalid, ICE on invalid Date: Sun, 19 Jan 2014 11:29:00 -0000 [thread overview] Message-ID: <bug-34547-4-9D4GlI5d7R@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-34547-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34547 --- Comment #13 from Paul Thomas <pault at gcc dot gnu.org> --- Author: pault Date: Sun Jan 19 11:28:44 2014 New Revision: 206772 URL: http://gcc.gnu.org/viewcvs?rev=206772&root=gcc&view=rev Log: 2014-01-19 Paul Thomas <pault@gcc.gnu.org> PR fortran/34547 * resolve.c (resolve_transfer): EXPR_NULL is always in an invalid context in a transfer statement. 2014-01-19 Paul Thomas <pault@gcc.gnu.org> PR fortran/34547 * gfortran.dg/null_5.f90 : Include new error. * gfortran.dg/null_6.f90 : Include new error. Modified: branches/gcc-4_8-branch/gcc/fortran/ChangeLog branches/gcc-4_8-branch/gcc/fortran/resolve.c branches/gcc-4_8-branch/gcc/testsuite/ChangeLog branches/gcc-4_8-branch/gcc/testsuite/gfortran.dg/null_5.f90 branches/gcc-4_8-branch/gcc/testsuite/gfortran.dg/null_6.f90
next prev parent reply other threads:[~2014-01-19 11:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-34547-4@http.gcc.gnu.org/bugzilla/> 2011-09-14 6:28 ` [Bug fortran/34547] " burnus at gcc dot gnu.org 2011-09-14 6:29 ` burnus at gcc dot gnu.org 2011-09-14 7:21 ` burnus at gcc dot gnu.org 2013-06-25 17:48 ` dominiq at lps dot ens.fr 2013-08-25 16:01 ` [Bug fortran/34547] [4.8/4.9 regression] " mikael at gcc dot gnu.org 2013-09-06 11:26 ` rguenth at gcc dot gnu.org 2013-10-16 9:48 ` jakub at gcc dot gnu.org 2013-12-01 10:53 ` burnus at gcc dot gnu.org 2014-01-19 11:29 ` pault at gcc dot gnu.org [this message] 2014-01-19 11:31 ` pault 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-34547-4-9D4GlI5d7R@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).