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 middle-end/94465] [10 Regression] fnsplit dump file ICEs Date: Fri, 03 Apr 2020 11:30:54 +0000 [thread overview] Message-ID: <bug-94465-4-K0sF3P7pQd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94465-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94465 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED Target Milestone|--- |10.0 Last reconfirmed| |2020-04-03 Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- The issue is that the SSA name is released: arg:1 <ssa_name 0xffffb7ba1480 type <error_mark 0xffffb7b9ed80> nothrow def_stmt version:3 in-free-list> so we're dumping something that was freed. Indeed we're dumping from delete_basic_block and there from cleanup_control_flow_pre which fails to delete unreachable basic-blocks in postorder which likely only matters for dumping.
next prev parent reply other threads:[~2020-04-03 11:30 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-03 10:49 [Bug middle-end/94465] New: " tnfchris at gcc dot gnu.org 2020-04-03 11:30 ` rguenth at gcc dot gnu.org [this message] 2020-04-03 13:24 ` [Bug middle-end/94465] " cvs-commit at gcc dot gnu.org 2020-04-03 13:25 ` rguenth at gcc dot gnu.org 2020-04-03 13:59 ` tnfchris 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-94465-4-K0sF3P7pQd@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).