public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/106751] [10/11/12/13 Regression] internal compiler error: in purge_dead_edges with inline-asm goto Date: Thu, 15 Dec 2022 13:10:31 +0000 [thread overview] Message-ID: <bug-106751-4-ICfP1isVGS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106751-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106751 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|needs-bisection | Priority|P3 |P2 CC| |jakub at gcc dot gnu.org Summary|internal compiler error: in |[10/11/12/13 Regression] |purge_dead_edges with |internal compiler error: in |inline-asm goto |purge_dead_edges with | |inline-asm goto Target Milestone|--- |10.5 --- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Reduced testcase that ICEs on x86_64-linux too (-O2): int *foo (void); void bar (void) { asm goto ("" : : : : lab); __builtin_unreachable (); lab: while (1) { int o; asm ("" : "=r" (o) : "g" (1)); *foo () = o; } } Started with r0-128630-ga3afdbb80906a5553a64f9ba7686a57d2f43f536
next prev parent reply other threads:[~2022-12-15 13:10 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-26 10:09 [Bug c/106751] New: internal compiler error: in purge_dead_edges, at cfgrtl.cc:3347 christophe.leroy at csgroup dot eu 2022-08-26 10:10 ` [Bug c/106751] " christophe.leroy at csgroup dot eu 2022-08-26 12:20 ` [Bug target/106751] " christophe.leroy at csgroup dot eu 2022-08-26 12:38 ` marxin at gcc dot gnu.org 2022-08-26 18:07 ` [Bug middle-end/106751] internal compiler error: in purge_dead_edges with inline-asm goto pinskia at gcc dot gnu.org 2022-08-26 18:08 ` pinskia at gcc dot gnu.org 2022-08-26 18:14 ` [Bug rtl-optimization/106751] " pinskia at gcc dot gnu.org 2022-08-26 18:21 ` pinskia at gcc dot gnu.org 2022-09-13 15:50 ` segher at gcc dot gnu.org 2022-12-15 13:10 ` jakub at gcc dot gnu.org [this message] 2022-12-15 15:51 ` [Bug rtl-optimization/106751] [10/11/12/13 Regression] " jakub at gcc dot gnu.org 2022-12-15 16:53 ` jakub at gcc dot gnu.org 2022-12-15 18:05 ` rguenth at gcc dot gnu.org 2022-12-16 9:20 ` cvs-commit at gcc dot gnu.org 2022-12-16 9:23 ` [Bug rtl-optimization/106751] [10/11/12 " jakub at gcc dot gnu.org 2023-02-10 17:44 ` cvs-commit at gcc dot gnu.org 2023-02-10 17:56 ` [Bug rtl-optimization/106751] [10/11 " jakub at gcc dot gnu.org 2023-05-02 20:12 ` cvs-commit at gcc dot gnu.org 2023-05-03 9:26 ` [Bug rtl-optimization/106751] [10 " jakub at gcc dot gnu.org 2023-05-03 15:20 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:19 ` jakub 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-106751-4-ICfP1isVGS@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).