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/53589] New: [4.7/4.8 Regression] ICE in maybe_record_trace_start with asm goto Date: Wed, 06 Jun 2012 12:53:00 -0000 [thread overview] Message-ID: <bug-53589-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53589 Bug #: 53589 Summary: [4.7/4.8 Regression] ICE in maybe_record_trace_start with asm goto Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: rtl-optimization AssignedTo: jakub@gcc.gnu.org ReportedBy: jakub@gcc.gnu.org extern void foo (void) __attribute__ ((__noreturn__)); void bar (int x) { if (x < 0) foo (); if (x == 0) return; __asm goto ("" : : : : lab); lab:; } ICEs on x86_64-linux: LC_ALL=C ./cc1 -O2 rh829247.c -quiet rh829247.c: In function 'bar': rh829247.c:12:1: internal compiler error: in maybe_record_trace_start, at dwarf2cfi.c:2193 } ^ Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. The problem is that we end up with asm goto that branches to the fallthru label and shrink-wrapping wants to redirect the edge, but leaves broken CFG around.
next reply other threads:[~2012-06-06 12:53 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-06 12:53 jakub at gcc dot gnu.org [this message] 2012-06-06 13:11 ` [Bug rtl-optimization/53589] " jakub at gcc dot gnu.org 2012-06-06 13:17 ` jakub at gcc dot gnu.org 2012-06-12 7:53 ` jakub at gcc dot gnu.org 2012-06-14 8:42 ` rguenth at gcc dot gnu.org 2012-06-14 17:50 ` jakub at gcc dot gnu.org 2012-06-15 11:11 ` 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-53589-4@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).