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/106982] New: [OpenACC] ICE incorrect sharing of tree nodes with nested reduction / .GOACC_REDUCTION Date: Tue, 20 Sep 2022 17:07:50 +0000 [thread overview] Message-ID: <bug-106982-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106982 Bug ID: 106982 Summary: [OpenACC] ICE incorrect sharing of tree nodes with nested reduction / .GOACC_REDUCTION Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code, openacc Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: tschwinge at gcc dot gnu.org Target Milestone: --- ICE with gcc/g++ -fopenacc: share10.i:6:9: error: incorrect sharing of tree nodes 6 | #pragma acc loop worker reduction(*:reduced) | ^~~ MEM <double[5]> [(double *)&reduced] MEM <double[5]> [(double *)&reduced] = .GOACC_REDUCTION (SETUP, 0, MEM <double[5]> [(double *)&reduced], -1, 73, 0); share10.i:6:9: error: incorrect sharing of tree nodes ----------- Failing code is ------------- int test1(double *c) { double reduced[5]; #pragma acc parallel loop gang private(reduced) for (int x = 0; x < 5; ++x) #pragma acc loop worker reduction(*:reduced) for (int y = 0; y < 5; ++y) { } }
next reply other threads:[~2022-09-20 17:07 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-20 17:07 burnus at gcc dot gnu.org [this message] 2022-09-21 7:49 ` [Bug middle-end/106982] [10/11/12/13 Regression][OpenACC] " rguenth at gcc dot gnu.org 2022-09-23 18:17 ` burnus at gcc dot gnu.org 2022-09-26 10:45 ` cvs-commit at gcc dot gnu.org 2022-09-29 11:48 ` cvs-commit at gcc dot gnu.org 2022-12-22 14:38 ` [Bug middle-end/106982] [10/11 " rguenth at gcc dot gnu.org 2022-12-22 14:39 ` rguenth at gcc dot gnu.org 2023-07-07 10:43 ` [Bug middle-end/106982] [11 " 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-106982-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).