public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus 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, 01 Dec 2013 10:53:00 -0000	[thread overview]
Message-ID: <bug-34547-4-kAbN9mRqHA@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 #11 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #8)
> Confirmed, however compiling the second test in comment #0, namely
> 
>  integer, allocatable :: i(:)
>  print *, NULL(i)
> end
> gives an ICE with 4.8.1 and trunk (4.9)


"If an input item is a pointer, it shall be associated with a definable target
and data are transferred from the file to the associated target. If an output
item is a pointer, it shall be associated with a target and data are
transferred
from the target to the file." (F2008, "9.6.3 Data transfer input/output list")

And NULL(...) isn't. Fixed by Paul's patch at
http://gcc.gnu.org/ml/fortran/2013-11/msg00203.html


  parent reply	other threads:[~2013-12-01 10:53 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 [this message]
2014-01-19 11:29 ` pault at gcc dot gnu.org
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-kAbN9mRqHA@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: 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).