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/111465] [14 regression] stage 3 ICE kills bootstrap from r14-4089-gd45ddc2c04e471d0dcee01 Date: Fri, 24 Nov 2023 15:13:32 +0000 [thread overview] Message-ID: <bug-111465-4-dcbN6NnD4z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111465-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111465 --- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:152400decc8383aeff9a9ad8262b9e7e2fff61e0 commit r13-8096-g152400decc8383aeff9a9ad8262b9e7e2fff61e0 Author: Richard Biener <rguenther@suse.de> Date: Tue Sep 19 12:36:04 2023 +0200 tree-optimization/111465 - bougs jump threading with no-copy src block The following avoids to forward thread a path with a EDGE_NO_COPY_SRC_BLOCK block that became non-empty due to folding. PR tree-optimization/111465 * tree-ssa-threadupdate.cc (fwd_jt_path_registry::thread_block_1): Cancel the path when a EDGE_NO_COPY_SRC_BLOCK became non-empty. * g++.dg/torture/pr111465.C: New testcase. (cherry picked from commit 564ecb7d5afb0bb4eb39285ce65c631490e37dce)
prev parent reply other threads:[~2023-11-24 15:13 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-18 20:26 [Bug bootstrap/111465] New: [14 regression] stage 3 ICE kills bootstrap seurer at gcc dot gnu.org 2023-09-18 20:48 ` [Bug tree-optimization/111465] " pinskia at gcc dot gnu.org 2023-09-18 21:41 ` seurer at gcc dot gnu.org 2023-09-18 21:54 ` pinskia at gcc dot gnu.org 2023-09-18 22:32 ` [Bug tree-optimization/111465] [14 regression] stage 3 ICE kills bootstrap from r14-4089-gd45ddc2c04e471d0dcee01 pinskia at gcc dot gnu.org 2023-09-18 22:40 ` pinskia at gcc dot gnu.org 2023-09-18 23:23 ` pinskia at gcc dot gnu.org 2023-09-18 23:30 ` pinskia at gcc dot gnu.org 2023-09-19 9:16 ` rguenth at gcc dot gnu.org 2023-09-19 10:19 ` rguenth at gcc dot gnu.org 2023-09-19 10:39 ` rguenth at gcc dot gnu.org 2023-09-19 11:24 ` cvs-commit at gcc dot gnu.org 2023-09-19 11:24 ` rguenth at gcc dot gnu.org 2023-11-24 15:13 ` cvs-commit at gcc dot gnu.org [this message]
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-111465-4-dcbN6NnD4z@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).