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 fortran/104717] [9/10/11/12 Regression] ICE: verify_ssa failed (Error: type mismatch between an SSA_NAME and its symbol) Date: Mon, 25 Apr 2022 21:14:43 +0000 [thread overview] Message-ID: <bug-104717-4-yRBZOO81dD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104717-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104717 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Thomas Schwinge <tschwinge@gcc.gnu.org>: https://gcc.gnu.org/g:b2202431910e30d8505c94d1cb9341cac7080d10 commit r12-8252-gb2202431910e30d8505c94d1cb9341cac7080d10 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Apr 20 19:06:17 2022 +0200 fortran: Fix up gfc_trans_oacc_construct [PR104717] So that move_sese_region_to_fn works properly, OpenMP/OpenACC constructs for which that function is invoked need an extra artificial BIND_EXPR around their body so that we move all variables of the bodies. The C/C++ FEs do that both for OpenMP constructs like OMP_PARALLEL, OMP_TASK or OMP_TARGET and for OpenACC constructs that behave similarly to OMP_TARGET, but the Fortran FE only does that for OpenMP constructs. The following patch does that for OpenACC constructs too. PR fortran/104717 gcc/fortran/ * trans-openmp.cc (gfc_trans_oacc_construct): Wrap construct body in an extra BIND_EXPR. gcc/testsuite/ * gfortran.dg/goacc/pr104717.f90: New test. * gfortran.dg/goacc/privatization-1-compute-loop.f90: Adjust. libgomp/ * testsuite/libgomp.oacc-fortran/privatized-ref-2.f90: Adjust. Co-authored-by: Thomas Schwinge <thomas@codesourcery.com>
next prev parent reply other threads:[~2022-04-25 21:14 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-28 12:32 [Bug tree-optimization/104717] New: " asolokha at gmx dot com 2022-02-28 13:09 ` [Bug tree-optimization/104717] [9/10/11/12 Regression] " jakub at gcc dot gnu.org 2022-02-28 13:47 ` tschwinge at gcc dot gnu.org 2022-03-01 8:02 ` rguenth at gcc dot gnu.org 2022-03-01 8:38 ` vries at gcc dot gnu.org 2022-03-01 11:01 ` vries at gcc dot gnu.org 2022-03-01 13:39 ` vries at gcc dot gnu.org 2022-03-01 15:28 ` vries at gcc dot gnu.org 2022-03-07 16:30 ` jakub at gcc dot gnu.org 2022-04-20 11:02 ` [Bug fortran/104717] " jakub at gcc dot gnu.org 2022-04-25 21:14 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-28 13:21 ` [Bug fortran/104717] [9/10/11 " cvs-commit at gcc dot gnu.org 2022-05-27 9:47 ` [Bug fortran/104717] [10/11 " rguenth at gcc dot gnu.org 2022-06-28 10:48 ` jakub at gcc dot gnu.org 2023-07-07 10:42 ` [Bug fortran/104717] [11 " rguenth at gcc dot gnu.org 2024-04-25 6:24 ` pault 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-104717-4-yRBZOO81dD@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).