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/98913] Create-temporary difference coarray/noncoarray – invalid code due to missing temporary
Date: Mon, 01 Feb 2021 11:51:33 +0000 [thread overview]
Message-ID: <bug-98913-4-qh0GWv9PdZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98913-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98913
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #0)
> D.3991 = (*(real(kind=8)[0:] * restrict) bb.data)[(bb.offset +
> (integer(kind=8)) j * bb.dim[1].stride) + (integer(kind=8)) k];
Missed that this one is a FP number not a pointer – hence, the issue I have
does not exist.
(Probably works – I have not verified whether that is always the case and I
hope it does.)
* * *
The difference between coarray and not occurs elsewhere: dependency.c's
gfc_dep_resolver has:
case REF_ARRAY:
/* For now, treat all coarrays as dangerous. */
if (lref->u.ar.codimen || rref->u.ar.codimen)
return 1;
Alternative would be to check for
flag_coarray == GFC_FCOARRAY_SINGLE
|| ref->u.ar.dimen_type[ref->u.ar.dimen] == DIMEN_THIS_IMAGE)
or something like that.
next prev parent reply other threads:[~2021-02-01 11:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 11:20 [Bug fortran/98913] New: " burnus at gcc dot gnu.org
2021-02-01 11:51 ` burnus at gcc dot gnu.org [this message]
2021-02-01 12:30 ` [Bug fortran/98913] " jdelia@santafe-conicet.gov.ar
2021-02-03 9:34 ` cvs-commit at gcc dot gnu.org
2021-02-03 9:36 ` [Bug fortran/98913] Create-temporary difference coarray/noncoarray – unnecessarily created temporary burnus 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-98913-4-qh0GWv9PdZ@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).