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/63158] Possible wrong code with absend optional BT_CLASS -> optional BT_DERIVED dummy argument
Date: Thu, 08 Oct 2015 10:05:00 -0000 [thread overview]
Message-ID: <bug-63158-4-JkSaPmYSaK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63158-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63158
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> I cannot find any file in gcc/fortran containing the string
> "!e->ref->u.ar.type != AR_FULL" for 4.8, 4.9 and trunk (5.0).
It has been replaced with "e->ref->u.ar.type != AR_FULL" at line 5218:
if (fsym->attr.optional
&& e->expr_type == EXPR_VARIABLE
&& (!e->ref
|| (e->ref->type == REF_ARRAY
&& e->ref->u.ar.type != AR_FULL))
&& e->symtree->n.sym->attr.optional)
Changed by r214827.
> Is this PR still valid?
*PING*!
Should I close this PR as INVALID to get an answer?
prev parent reply other threads:[~2015-10-08 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 18:49 [Bug fortran/63158] New: " burnus at gcc dot gnu.org
2015-03-06 13:38 ` [Bug fortran/63158] " dominiq at lps dot ens.fr
2015-09-04 9:11 ` dominiq at lps dot ens.fr
2015-10-08 10:05 ` 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-63158-4-JkSaPmYSaK@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).