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: Tue, 05 Dec 2023 07:30:12 +0000 [thread overview] Message-ID: <bug-112827-4-cJs94kjNu0@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 #7 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:50f2a3370d177f8fe9bea0461feb710523e048a2 commit r14-6132-g50f2a3370d177f8fe9bea0461feb710523e048a2 Author: Richard Biener <rguenther@suse.de> Date: Mon Dec 4 15:46:38 2023 +0100 tree-optimization/112827 - more SCEV cprop fixes The insert iteration can be corrupted by foldings of replace_uses_by, within this particular PHI replacement but also with subsequent ones. Recompute the insert location before insertion instead. This fixes an obvserved ICE of gcc.dg/tree-ssa/ssa-sink-16.c. PR tree-optimization/112827 PR tree-optimization/112848 * tree-scalar-evolution.cc (final_value_replacement_loop): Compute the insert location for each insert.
next prev parent reply other threads:[~2023-12-05 7:30 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 2023-12-04 11:54 ` rguenth at gcc dot gnu.org 2023-12-05 7:30 ` cvs-commit at gcc dot gnu.org [this message] 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-cJs94kjNu0@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).