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/110298] [10/11/12/13 Regression] ICE at -Os on x86_64-linux-gnu since r10-840 Date: Fri, 23 Jun 2023 10:30:12 +0000 [thread overview] Message-ID: <bug-110298-4-jPR0JBFBzT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110298-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110298 --- Comment #6 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:9da2ef362fa8dc54df26c704a38dda40baee3ce9 commit r13-7469-g9da2ef362fa8dc54df26c704a38dda40baee3ce9 Author: Richard Biener <rguenther@suse.de> Date: Mon Jun 19 09:52:45 2023 +0200 tree-optimization/110298 - CFG cleanup and stale nb_iterations When unrolling we eventually kill nb_iterations info since it may refer to removed SSA names. But we do this only after cleaning up the CFG which in turn can end up accessing it. Fixed by swapping the two. PR tree-optimization/110298 * tree-ssa-loop-ivcanon.cc (tree_unroll_loops_completely): Clear number of iterations info before cleaning up the CFG. * gcc.dg/torture/pr110298.c: New testcase. (cherry picked from commit 916add3bf6e46467e4391e358b11ecfbc4daa275)
next prev parent reply other threads:[~2023-06-23 10:30 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-17 14:29 [Bug c/110298] New: ICE at -Os on x86_64-linux-gnu shaohua.li at inf dot ethz.ch 2023-06-17 15:36 ` [Bug c/110298] [10/11/12/13/14 Regression] ICE at -Os on x86_64-linux-gnu since r10-840 jakub at gcc dot gnu.org 2023-06-17 18:09 ` [Bug tree-optimization/110298] " pinskia at gcc dot gnu.org 2023-06-17 18:22 ` pinskia at gcc dot gnu.org 2023-06-19 7:53 ` rguenth at gcc dot gnu.org 2023-06-19 11:02 ` cvs-commit at gcc dot gnu.org 2023-06-19 11:03 ` [Bug tree-optimization/110298] [10/11/12/13 " rguenth at gcc dot gnu.org 2023-06-23 10:30 ` cvs-commit at gcc dot gnu.org [this message] 2023-06-23 11:30 ` [Bug tree-optimization/110298] [10/11/12 " cvs-commit at gcc dot gnu.org 2023-07-07 10:45 ` [Bug tree-optimization/110298] [11 " rguenth at gcc dot gnu.org 2023-12-15 12:18 ` cvs-commit at gcc dot gnu.org 2023-12-15 12:20 ` 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-110298-4-jPR0JBFBzT@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).