public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/106982] [10/11/12/13 Regression][OpenACC] ICE incorrect sharing of tree nodes with nested reduction / .GOACC_REDUCTION Date: Thu, 29 Sep 2022 11:48:29 +0000 [thread overview] Message-ID: <bug-106982-4-MTbgTthBgu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106982-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106982 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>: https://gcc.gnu.org/g:afea1ae84f0c3e64137289c44c756195babe1845 commit r12-8793-gafea1ae84f0c3e64137289c44c756195babe1845 Author: Tobias Burnus <tobias@codesourcery.com> Date: Mon Sep 26 12:45:28 2022 +0200 OpenACC: Fix reduction tree-sharing issue [PR106982] The tree for var == incoming == outgound was 'MEM <double[5]> [(double *)&reduced]' which caused the ICE "incorrect sharing of tree nodes". PR middle-end/106982 gcc/ChangeLog: * omp-low.cc (lower_oacc_reductions): Add some unshare_expr. gcc/testsuite/ChangeLog: * c-c++-common/goacc/reduction-7.c: New test. * c-c++-common/goacc/reduction-8.c: New test. (cherry picked from commit d3df98807b58df186061ad52ff87cc09ba593e9b)
next prev parent reply other threads:[~2022-09-29 11:48 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-20 17:07 [Bug middle-end/106982] New: [OpenACC] " burnus at gcc dot gnu.org 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 [this message] 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-MTbgTthBgu@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).