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/99007] [8/9/10 Regression] ICE in dominated_by_p, at dominance.c:1124
Date: Fri, 19 Mar 2021 23:28:51 +0000 [thread overview]
Message-ID: <bug-99007-4-VEcMB0tDGK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99007-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99007
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:deba6b20a3889aa23f0e4b3a5248de4172a0167d
commit r10-9465-gdeba6b20a3889aa23f0e4b3a5248de4172a0167d
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Feb 10 10:34:58 2021 +0100
openmp: Temporarily disable into_ssa when gimplifying OpenMP reduction
clauses [PR99007]
gimplify_scan_omp_clauses was already calling gimplify_expr with false as
last argument to make sure it is not an SSA_NAME, but as the testcases
show,
that is not enough, SSA_NAME temporaries created during that gimplification
can be reused too and we can't allow SSA_NAMEs to be used across OpenMP
region boundaries, as we can only firstprivatize decls.
Fixed by temporarily disabling into_ssa.
2021-02-10 Jakub Jelinek <jakub@redhat.com>
PR middle-end/99007
* gimplify.c (gimplify_scan_omp_clauses): For MEM_REF on
reductions,
temporarily disable gimplify_ctxp->into_ssa around gimplify_expr
calls.
* g++.dg/gomp/pr99007.C: New test.
* gcc.dg/gomp/pr99007-1.c: New test.
* gcc.dg/gomp/pr99007-2.c: New test.
* gcc.dg/gomp/pr99007-3.c: New test.
(cherry picked from commit bd0e37f68a3aed944df4eb739a0734bb87153749)
next prev parent reply other threads:[~2021-03-19 23:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 18:14 [Bug c++/99007] New: [11 " gscfq@t-online.de
2021-02-08 18:19 ` [Bug c++/99007] " jakub at gcc dot gnu.org
2021-02-09 14:57 ` jakub at gcc dot gnu.org
2021-02-09 15:26 ` [Bug middle-end/99007] " jakub at gcc dot gnu.org
2021-02-09 16:30 ` jakub at gcc dot gnu.org
2021-02-10 9:42 ` cvs-commit at gcc dot gnu.org
2021-02-10 14:46 ` [Bug middle-end/99007] [8/9/10 " jakub at gcc dot gnu.org
2021-02-10 14:46 ` jakub at gcc dot gnu.org
2021-03-19 23:28 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-20 8:07 ` [Bug middle-end/99007] [8/9 " jakub at gcc dot gnu.org
2021-04-20 23:32 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:50 ` cvs-commit at gcc dot gnu.org
2021-04-22 17:11 ` 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-99007-4-VEcMB0tDGK@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: link
Be 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).