public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/35737] New: [4.3/4.3/4.4 regression] ICE with __builtin_setjmp and complex variable Date: Fri, 28 Mar 2008 18:30:00 -0000 [thread overview] Message-ID: <bug-35737-1771@http.gcc.gnu.org/bugzilla/> (raw) The following valid code snippet triggers an ICE since GCC 4.2.0 when compiled with "-O": ========================================= #include <setjmp.h> jmp_buf buf; int foo() { __complex__ int i = 0; if (__builtin_setjmp(buf)) { i = 1; bar(); } return i == 0; } ========================================= Corrupt SSA across abnormal edge BB2->BB7 Argument 0 (0) is not an SSA_NAME. bug.c: In function 'foo': bug.c:6: internal compiler error: SSA corruption Please submit a full bug report, [etc.] Maybe related to PR35314. -- Summary: [4.3/4.3/4.4 regression] ICE with __builtin_setjmp and complex variable Product: gcc Version: 4.4.0 Status: UNCONFIRMED Keywords: ice-on-valid-code, monitored Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: reichelt at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35737
next reply other threads:[~2008-03-28 18:30 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-03-28 18:30 reichelt at gcc dot gnu dot org [this message] 2008-03-28 18:30 ` [Bug tree-optimization/35737] " reichelt at gcc dot gnu dot org 2008-03-30 0:25 ` [Bug tree-optimization/35737] [4.2/4.3/4.4 " pinskia at gcc dot gnu dot org 2008-03-30 0:31 ` pinskia at gcc dot gnu dot org 2008-04-15 9:37 ` jakub at gcc dot gnu dot org 2008-05-19 20:35 ` jsm28 at gcc dot gnu dot org 2008-09-30 22:45 ` rth at gcc dot gnu dot org 2008-10-01 14:30 ` rth at gcc dot gnu dot org 2008-10-01 14:33 ` rth at gcc dot gnu dot org 2008-10-01 14:44 ` rth at gcc dot gnu dot org 2009-04-29 15:19 ` pinskia at gcc dot gnu dot 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-35737-1771@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).