public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92929] OpenACC/OpenMP 'target' 'exit data'/'update' optimizations
Date: Mon, 06 Jul 2020 16:19:36 +0000 [thread overview]
Message-ID: <bug-92929-4-QGnP9kMYVa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92929-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92929
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
Ever confirmed|0 |1
Last reconfirmed| |2020-07-06
Status|UNCONFIRMED |NEW
Depends on| |94635
--- Comment #8 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
In addition to r277631 "Fortran/OpenMP] Don't create "alloc:" for 'target exit
data'", as shown in the PR94635 commit af557050fd011a03d21dc26b31959033061a0443
"[OpenMP] Fix 'omp exit data' for Fortran arrays (PR 94635)", and commit
9f0f7da9aa98eec28b4e5e34ade0aa0028df161d "[OpenMP] Fix 'omp exit data' for
Fortran arrays (PR 94635)", this is not only an optimization but also a
correctness issue.
The OpenMP cases now presumably have been addressed, but OpenACC not yet?
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94635
[Bug 94635] [OpenMP][Offloading] mapping with alloc/delete followed by
map(from/tofrom:) fails
next prev parent reply other threads:[~2020-07-06 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-92929-4@http.gcc.gnu.org/bugzilla/>
2020-06-08 13:08 ` jules at gcc dot gnu.org
2020-07-06 16:19 ` tschwinge at gcc dot gnu.org [this message]
2020-07-06 16:37 ` tschwinge at gcc dot gnu.org
2020-07-14 12:51 ` tschwinge at gcc dot gnu.org
2022-01-09 0:34 ` pinskia 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-92929-4-QGnP9kMYVa@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).