public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97520] ICE in calc_stmt, at gimple-range.cc:399 with "-O1 -fno-tree-fre -ftree-vrp" Date: Wed, 21 Oct 2020 18:26:24 +0000 [thread overview] Message-ID: <bug-97520-4-LNNSYKmcHo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97520-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97520 Andrew Macleod <amacleod at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amacleod at redhat dot com --- Comment #1 from Andrew Macleod <amacleod at redhat dot com> --- Created attachment 49416 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49416&action=edit handle a_2 = &a We handle more complex memory processing like &(x_2 +1), but the very simple a_2 = &a_1 was slipping thru and we were creating the range based on a_1, not &a_1. Typically we never saw that since earlier passes were propagating this. turning off FRE exposed this situatuion. This patch should correct that... verifying now.
next prev parent reply other threads:[~2020-10-21 18:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-21 15:23 [Bug c/97520] New: " suochenyao at 163 dot com 2020-10-21 18:26 ` amacleod at redhat dot com [this message] 2020-10-21 18:34 ` [Bug tree-optimization/97520] " marxin at gcc dot gnu.org 2020-10-21 18:35 ` marxin at gcc dot gnu.org 2020-10-22 0:16 ` cvs-commit at gcc dot gnu.org 2020-10-22 7:03 ` rguenth at gcc dot gnu.org 2020-10-30 15:25 ` suochenyao at 163 dot com 2020-10-30 15:27 ` suochenyao at 163 dot com
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-97520-4-LNNSYKmcHo@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).