public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/100902] New: pointer attachment issues Date: Fri, 04 Jun 2021 11:12:56 +0000 [thread overview] Message-ID: <bug-100902-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100902 Bug ID: 100902 Summary: pointer attachment issues Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- On: void foo (int *ptr) { #pragma omp target map (ptr, ptr[:4]) #pragma omp parallel master ptr[0] = 1; } void bar (int *ptr) { #pragma omp target parallel map (ptr[:4], ptr) #pragma omp master ptr[0] = 1; } foo is compiled fine, but bar ICEs because c_omp_adjust_map_clauses isn't called on the combined constructs. Another bug is that void baz (int *ptr) { #pragma omp target map (ptr[:4], ptr) #pragma omp parallel master ptr[0] = 1; } void qux (int *ptr) { #pragma omp target parallel map (ptr, ptr[:4]) #pragma omp master ptr[0] = 1; } is rejected by both C and C++ pointers twice with ‘ptr’ appears both in data and map clauses The user ordering of clauses (which is reversed for the non-combined cases in the implementation) should not matter. I'll deal with the bar issue for now.
next reply other threads:[~2021-06-04 11:12 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-04 11:12 jakub at gcc dot gnu.org [this message] 2021-06-04 12:46 ` [Bug c/100902] " jakub at gcc dot gnu.org 2021-06-06 17:37 ` cvs-commit at gcc dot gnu.org 2021-06-17 5:59 ` cvs-commit at gcc dot gnu.org 2022-05-07 7:37 ` jakub 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-100902-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).