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/112827] [14 Regression] ICE on valid code at -O1 on x86_64-linux-gnu: Segmentation fault
Date: Mon, 04 Dec 2023 11:54:23 +0000 [thread overview]
Message-ID: <bug-112827-4-OQjO55GoCQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112827-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112827
--- Comment #5 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:de0ab339a795352c843f6e9b2dfce222f26588de
commit r14-6114-gde0ab339a795352c843f6e9b2dfce222f26588de
Author: Richard Biener <rguenther@suse.de>
Date: Mon Dec 4 10:46:11 2023 +0100
tree-optimization/112827 - corrupt SCEV cache during SCCP
The following avoids corrupting the SCEV cache by my last change
to propagate constant final values immediately. The easiest fix
is to keep a dead initialization around.
PR tree-optimization/112827
* tree-scalar-evolution.cc (final_value_replacement_loop):
Do not release SSA name but keep a dead initialization around.
* gcc.dg/torture/pr112827-1.c: New testcase.
* gcc.dg/torture/pr112827-2.c: Likewise.
next prev parent reply other threads:[~2023-12-04 11:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 18:43 [Bug tree-optimization/112827] New: " zhendong.su at inf dot ethz.ch
2023-12-02 18:50 ` [Bug tree-optimization/112827] [14 Regression] " pinskia at gcc dot gnu.org
2023-12-03 9:18 ` zhendong.su at inf dot ethz.ch
2023-12-04 7:04 ` rguenth at gcc dot gnu.org
2023-12-04 9:44 ` rguenth at gcc dot gnu.org
2023-12-04 11:54 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-04 11:54 ` rguenth at gcc dot gnu.org
2023-12-05 7:30 ` cvs-commit at gcc dot gnu.org
2023-12-09 15:55 ` 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-112827-4-OQjO55GoCQ@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).