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 middle-end/113867] [14 Regression][OpenMP] Wrong code with mapping pointers in structs Date: Sat, 10 Feb 2024 18:07:42 +0000 [thread overview] Message-ID: <bug-113867-4-UjoXvXzGKA@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 #1 from Tobias Burnus <burnus at gcc dot gnu.org> --- Created attachment 57382 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57382&action=edit Fortran testcase, kind of, as pointer + pointee mapping cannot be split (working) For completeness, a Fortran testcase. (This Testcase works on GCC 13 and mainline.) As in Fortran, 'map(ptr, dt%ptr)' will always attempt to map the pointer and the pointer, it is not possible to split map(s2.p[:N]) // map the pointee map(s2.p, s2.p[:0]) // map the pointer and try pointer attachment as in C/C++. And using 'map(s.p)' will prevent a later inner 'map(s.a,...)' as 's' is already partially mapped. Hence, the aux 'ptr' is used, but that kind of defeats the purpose of this testcase.
next prev parent reply other threads:[~2024-02-10 18:07 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 ` burnus at gcc dot gnu.org [this message] 2024-02-12 8:45 ` [Bug middle-end/113867] " 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 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-UjoXvXzGKA@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).