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 tree-optimization/98268] [10 Regression] ICE: verify_gimple failed with LTO and SVE
Date: Fri, 23 Apr 2021 09:10:35 +0000 [thread overview]
Message-ID: <bug-98268-4-c95B8BKag3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98268-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98268
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Richard Sandiford
<rsandifo@gcc.gnu.org>:
https://gcc.gnu.org/g:18a190c3ee32548de3888b7a64f701999893727b
commit r10-9750-g18a190c3ee32548de3888b7a64f701999893727b
Author: Richard Sandiford <richard.sandiford@arm.com>
Date: Fri Apr 23 10:09:39 2021 +0100
gimple-fold: Recompute ADDR_EXPR flags after folding a TMR [PR98268]
The gimple verifier picked up that an ADDR_EXPR of a MEM_REF was not
marked TREE_CONSTANT even though the address was in fact invariant.
This came from folding a &TARGET_MEM_REF with constant operands to
a &MEM_REF; &TARGET_MEM_REF is never treated as TREE_CONSTANT
but &MEM_REF can be.
gcc/
PR tree-optimization/98268
* gimple-fold.c (maybe_canonicalize_mem_ref_addr): Call
recompute_tree_invariant_for_addr_expr after successfully
folding a TARGET_MEM_REF that occurs inside an ADDR_EXPR.
gcc/testsuite/
PR tree-optimization/98268
* gcc.target/aarch64/sve/pr98268-1.c: New test.
* gcc.target/aarch64/sve/pr98268-2.c: Likewise.
(cherry picked from commit c778968339afd140380a46edbade054667c7dce2)
next prev parent reply other threads:[~2021-04-23 9:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 8:16 [Bug tree-optimization/98268] New: " acoplan at gcc dot gnu.org
2021-01-04 14:33 ` [Bug tree-optimization/98268] " rguenth at gcc dot gnu.org
2021-01-04 15:01 ` acoplan at gcc dot gnu.org
2021-01-18 10:07 ` acoplan at gcc dot gnu.org
2021-01-18 10:42 ` [Bug tree-optimization/98268] [10 Regression] " ktkachov at gcc dot gnu.org
2021-01-18 10:47 ` acoplan at gcc dot gnu.org
2021-01-18 10:49 ` [Bug tree-optimization/98268] [10/11 " ktkachov at gcc dot gnu.org
2021-03-30 17:11 ` rsandifo at gcc dot gnu.org
2021-03-31 18:34 ` cvs-commit at gcc dot gnu.org
2021-03-31 20:36 ` [Bug tree-optimization/98268] [10 " rsandifo at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-04-23 9:10 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-23 9:12 ` rsandifo 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-98268-4-c95B8BKag3@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).