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/110639] New: [OpenMP][5.1] Predefined firstprivate for pointers - attachment missing Date: Wed, 12 Jul 2023 09:32:58 +0000 [thread overview] Message-ID: <bug-110639-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110639 Bug ID: 110639 Summary: [OpenMP][5.1] Predefined firstprivate for pointers - attachment missing Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: openmp, wrong-code Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org Target Milestone: --- OpenMP 5.1 changed (quoting GCC impl. status): Pointer predetermined firstprivate getting initialized to address of matching mapped list item per 5.1, Sect. 2.21.7.2 However, looking at the examples in the OpenMP spec issue #1796 (TRAC864) this does not handle partially mapped data correctly: int a[100]; int *p = &a[0]; #pragma omp target teams distribute map(a[start:n]) for (int i = start; i < start+n; i++) { p[i] = f(p[i], i); } Here, 'p' has an points to 'a' (actually, to the base address of 'a') but this address is not mapped. However, it still points to the extended address range of mapped data.
next reply other threads:[~2023-07-12 9:32 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-12 9:32 burnus at gcc dot gnu.org [this message] 2023-11-21 15:57 ` [Bug middle-end/110639] " burnus at gcc dot gnu.org 2023-11-21 16:31 ` burnus at gcc dot gnu.org 2023-12-05 13:57 ` burnus at gcc dot gnu.org 2023-12-06 15:43 ` burnus at gcc dot gnu.org 2023-12-11 11:57 ` 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-110639-4@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).