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/45859] [Coarray, F2008, IR] Rejects valid actuals to coarray dummies
Date: Tue, 20 Oct 2015 16:45:00 -0000 [thread overview]
Message-ID: <bug-45859-4-lxbGkq7fLF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45859-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45859
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2015-10-20
Ever confirmed|0 |1
--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> With current gfortran 4.7, the "x(10:)" program is accepted and the other
> one is rejected for "x(10)" with "must be simply contiguous" (which is true).
> Thus, the result is OK and only depends on what J3/WG5 regard as correct.
Confirmed from 4.8 up to trunk (6.0).
> TODO: Wait for the result of the IR.
>From my version of the Fortran 2015 draft
12.5.2.8 Coarray dummy variables
...
2 If the dummy argument is an array coarray that has the CONTIGUOUS attribute
or is not of assumed shape, the corresponding actual argument shall be simply
contiguous or an element of a simply contiguous array.
Does it means that gfortran is correct?
prev parent reply other threads:[~2015-10-20 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 15:55 [Bug fortran/45859] New: " burnus at gcc dot gnu.org
2011-03-27 17:32 ` [Bug fortran/45859] " burnus at gcc dot gnu.org
2011-07-18 20:16 ` burnus at gcc dot gnu.org
2011-07-18 20:21 ` burnus at gcc dot gnu.org
2011-08-25 15:01 ` burnus at gcc dot gnu.org
2015-10-20 16:45 ` dominiq at lps dot ens.fr [this message]
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-45859-4-lxbGkq7fLF@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).