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 libgomp/109646] OpenACC attach directive fails with "pointer target not mapped for attach" Date: Fri, 28 Apr 2023 13:04:35 +0000 [thread overview] Message-ID: <bug-109646-4-JxKYfGt8tX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109646-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109646 Thomas Schwinge <tschwinge at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=109622 Status|UNCONFIRMED |WAITING CC| |burnus at gcc dot gnu.org, | |jules at gcc dot gnu.org, | |tschwinge at gcc dot gnu.org Last reconfirmed| |2023-04-28 --- Comment #2 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- This sounds as if it may've been fixed (for GCC master branch) via today's PR109622 "[OpenACC] internal compiler error: in omp_group_base, at gimplify.cc:9412 if -fopenacc is set" commit r14-325-gcacf65d74463600815773255e8b82b4043432bd7 "OpenACC: Stand-alone attach/detach clause fixes for Fortran [PR109622]"? Please check.
next prev parent reply other threads:[~2023-04-28 13:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-27 10:37 [Bug libgomp/109646] New: " patrick.begou@univ-grenoble-alpes.fr 2023-04-27 13:18 ` [Bug libgomp/109646] " patrick.begou@univ-grenoble-alpes.fr 2023-04-28 13:04 ` tschwinge at gcc dot gnu.org [this message] 2023-04-29 9:43 ` patrick.begou@univ-grenoble-alpes.fr 2023-05-08 12:37 ` tschwinge at gcc dot gnu.org 2023-05-08 13:50 ` patrick.begou@univ-grenoble-alpes.fr 2023-05-08 13:58 ` 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-109646-4-JxKYfGt8tX@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: linkBe 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).