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 tree-optimization/104717] [9/10/11/12 Regression] ICE: verify_ssa failed (Error: type mismatch between an SSA_NAME and its symbol) Date: Mon, 07 Mar 2022 16:30:13 +0000 [thread overview] Message-ID: <bug-104717-4-EcOU4TSe4P@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 #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- As A.3 is in the body of a construct that is outlined into a separate function, it should be moved to the *omp_fn* function with it. If you look at simple int main () { #pragma omp parallel { int a = 25; ++a; } } you can see in the gimple dump two pairs of {}s instead of just once: #pragma omp parallel { { int a; a = 25; a = a + 1; } } (ditto target, task, (host) teams etc.), while with acc parallel that isn't the case: #pragma omp target oacc_parallel map(from:(*array.12_5) [len: D.4276]) map(alloc:array [pointer assign, bias: 0]) firstprivate(ubound.0) firstprivate(nn) { The reason for that for the OpenMP construct is exactly to ensure that move_sese_region_to_fn does the right thing with it.
next prev parent reply other threads:[~2022-03-07 16:30 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 [this message] 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 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-EcOU4TSe4P@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).