public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libgomp/93305] [OpenACC] 'acc_shutdown' vs. active data lifetimes
[not found] <bug-93305-4@http.gcc.gnu.org/bugzilla/>
@ 2020-07-21 15:41 ` tschwinge at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: tschwinge at gcc dot gnu.org @ 2020-07-21 15:41 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93305
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://github.com/OpenACC/
| |openacc-spec/issues/102
Last reconfirmed|2020-01-20 00:00:00 |2020-7-21
--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to Thomas Schwinge from comment #0)
> It's less clear what should happen when after an 'acc_shutdown' we then
> again (implicitly/explicitly) 'acc_init': how/which state gets restored?
Discussion in <https://github.com/OpenACC/openacc-spec/issues/102> is relevant.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-07-21 15:41 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-93305-4@http.gcc.gnu.org/bugzilla/>
2020-07-21 15:41 ` [Bug libgomp/93305] [OpenACC] 'acc_shutdown' vs. active data lifetimes tschwinge at gcc dot gnu.org
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).