public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/111942] ICE in rtl_split_edge, at cfgrtl.cc:1943 on pr98096.c with new -fharden-control-flow-redundancy with asm goto Date: Thu, 26 Oct 2023 07:39:12 +0000 [thread overview] Message-ID: <bug-111942-4-e69zERhx7X@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111942-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111942 Alexandre Oliva <aoliva at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2023-10-26 Ever confirmed|0 |1 --- Comment #1 from Alexandre Oliva <aoliva at gcc dot gnu.org> --- Thanks for the report. This latent bug is independent from -fharden-control-flow-redundancy. The issue is that volatile asm stmts are considered throw points when -fnon-call-exceptions is enabled. I'm not sure where C++ wires non-call exceptions to enclosing handlers, but it appears that it doesn't: even with a handler added around f's body, no EH edges are added. However, inlining f() into another function with a handler for the call will wire all escaping exceptions to that handler, creating the same arrangement of 3 outgoing edges (fallthrough, asm jmp, and EH) that the rtl splitter barfs at. /* compile with -fnon-call-exceptions */ int i, j; int f(void) { asm goto ("# %0 %2" : "+r" (i) ::: jmp); i += 2; asm goto ("# %0 %1 %l[jmp]" : "+r" (i), "+r" (j) ::: jmp); jmp: return i; } int inline __attribute__ ((__always_inline__)) f(void); int g(void) { try { return f(); } catch (...) { i++; throw; } } ./xgcc -B./ pr98096.cc -fno-harden-control-flow-redundancy -fnon-call-exceptions during RTL pass: expand pr98096.cc: In function ‘int g()’: pr98096.cc:19:1: internal compiler error: in rtl_split_edge, at cfgrtl.cc:1943 19 | }
prev parent reply other threads:[~2023-10-26 7:39 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-23 18:45 [Bug rtl-optimization/111942] New: ICE in rtl_split_edge, at cfgrtl.cc:1943 on pr98096.c with new -fharden-control-flow-redundancy mjires at suse dot cz 2023-10-26 7:39 ` aoliva 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-111942-4-e69zERhx7X@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).