public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114998] [14/15 Regression] ICE on valid code at -O3 with "-fno-tree-dce" on x86_64-linux-gnu: Segmentation fault since r14-9767 Date: Fri, 10 May 2024 11:14:24 +0000 [thread overview] Message-ID: <bug-114998-4-tlGCxqM9GA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114998-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114998 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- Breakpoint 5, release_ssa_name_fn (fn=0x7ffff6be4000, var=<ssa_name 0x7ffff6bebea0 52>) at ../../src/gcc-14-branch/gcc/tree-ssanames.cc:619 619 vec_safe_push (FREE_SSANAMES_QUEUE (fn), var); (gdb) p v.m_vecpfx $7 = {m_alloc = 127, m_using_auto_storage = 0, m_num = 4294967295} The issue is that loop distribution removes stmts from the last partition (with the original stmts in the IL), and during cleanup in free_rdg sets stmt UIDs to -1 again, but also to stmts that were released. The simplest fix I think is to not re-set UIDs in free_rdg.
next prev parent reply other threads:[~2024-05-10 11:14 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-08 21:38 [Bug tree-optimization/114998] New: ICE on valid code at -O3 with "-fno-inline -fno-tree-dce -fno-ipa-cp" on x86_64-linux-gnu: Segmentation fault zhendong.su at inf dot ethz.ch 2024-05-09 8:05 ` [Bug tree-optimization/114998] [14/15 Regression] ICE on valid code at -O3 with "-fno-tree-dce" " pinskia at gcc dot gnu.org 2024-05-09 10:09 ` [Bug tree-optimization/114998] [14/15 Regression] ICE on valid code at -O3 with "-fno-tree-dce" on x86_64-linux-gnu: Segmentation fault since r14-9767 jakub at gcc dot gnu.org 2024-05-10 6:49 ` rguenth at gcc dot gnu.org 2024-05-10 11:14 ` rguenth at gcc dot gnu.org [this message] 2024-05-10 13:44 ` cvs-commit at gcc dot gnu.org 2024-05-10 13:44 ` [Bug tree-optimization/114998] [14 " rguenth at gcc dot gnu.org 2024-05-17 10:39 ` cvs-commit at gcc dot gnu.org 2024-05-17 10:39 ` 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-114998-4-tlGCxqM9GA@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).