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 libgomp/113867] [14 Regression][OpenMP] Wrong code with mapping pointers in structs Date: Tue, 13 Feb 2024 10:43:25 +0000 [thread overview] Message-ID: <bug-113867-4-dLadqmX7O3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113867-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113867 --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> --- Also not handled: struct s { int *p; } s1; ... #pragma omp target map(s1.p[:N]) p[0] = p[N-1] = 99; Here, the pointer attachment is missing. See also PR113724 's attachment 57407 for a testcase for this and (some) other issues. TODO: - Fix the extra struct issue (→ this patch or other solution) - Fix the missing attachment issue (this comment's example) - Audit whether other changes are required.
next prev parent reply other threads:[~2024-02-13 10:43 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-10 18:01 [Bug middle-end/113867] New: " burnus at gcc dot gnu.org 2024-02-10 18:07 ` [Bug middle-end/113867] " burnus at gcc dot gnu.org 2024-02-12 8:45 ` rguenth at gcc dot gnu.org 2024-02-12 12:30 ` [Bug libgomp/113867] " burnus at gcc dot gnu.org 2024-02-12 13:00 ` burnus at gcc dot gnu.org 2024-02-13 10:43 ` burnus at gcc dot gnu.org [this message] 2024-02-21 17:59 ` burnus at gcc dot gnu.org 2024-03-07 20:40 ` law at gcc dot gnu.org 2024-04-03 12:02 ` rguenth at gcc dot gnu.org 2024-04-26 8:42 ` jakub at gcc dot gnu.org 2024-05-07 7:45 ` [Bug libgomp/113867] [14/15 " rguenth 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-113867-4-dLadqmX7O3@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).