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/113707] [14 Regression] ICE on valid code at -O1 on x86_64-linux-gnu: Segmentation fault since r14-8683
Date: Mon, 05 Feb 2024 10:07:22 +0000 [thread overview]
Message-ID: <bug-113707-4-1YfWM3ptFQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113707-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113707
--- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:42959acb8409c39e1c71c43528832611c3b71e25
commit r14-8800-g42959acb8409c39e1c71c43528832611c3b71e25
Author: Richard Biener <rguenther@suse.de>
Date: Mon Feb 5 09:44:12 2024 +0100
tree-optimization/113707 - ICE with VN elimination
The following avoids different avail answers depending on how the
iteration progressed.
PR tree-optimization/113707
* tree-ssa-sccvn.cc (rpo_elim::eliminate_avail): After
checking the avail set treat out-of-region defines as
available.
* gcc.dg/torture/pr113707-1.c: New testcase.
* gcc.dg/torture/pr113707-2.c: Likewise.
next prev parent reply other threads:[~2024-02-05 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 15:58 [Bug tree-optimization/113707] New: ICE on valid code at -O1 on x86_64-linux-gnu: Segmentation fault zhendong.su at inf dot ethz.ch
2024-02-01 16:10 ` [Bug tree-optimization/113707] [14 Regression] ICE on valid code at -O1 on x86_64-linux-gnu: Segmentation fault since r14-8683 jakub at gcc dot gnu.org
2024-02-01 17:40 ` zhendong.su at inf dot ethz.ch
2024-02-05 8:24 ` rguenth at gcc dot gnu.org
2024-02-05 8:44 ` rguenth at gcc dot gnu.org
2024-02-05 8:51 ` rguenth at gcc dot gnu.org
2024-02-05 10:07 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-05 10:08 ` rguenth 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-113707-4-1YfWM3ptFQ@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).