public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, malekith@pld.org.pl, nobody@gcc.gnu.org Subject: Re: optimization/4382: [3.2/3.3 regression] __builtin_{set,long}jmp with -O3 can crash the compiler Date: Fri, 06 Dec 2002 15:55:00 -0000 [thread overview] Message-ID: <20021206235505.4985.qmail@sources.redhat.com> (raw) Old Synopsis: __builtin_{set,long}jmp with -O3 can crash the compiler New Synopsis: [3.2/3.3 regression] __builtin_{set,long}jmp with -O3 can crash the compiler State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Fri Dec 6 15:55:04 2002 State-Changed-Why: Confirmed. I get with 3.2.2pre and 3.3pre: tmp/g> /home/bangerth/bin/gcc-3.2.2-pre/bin/gcc -c -O3 x.c x.c: In function `main': x.c:21: Internal compiler error in make_edges, at cfgbuild.c:402 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. tmp/g> tmp/g> tmp/g> tmp/g> /home/bangerth/bin/gcc-3.3-pre/bin/gcc -c -O3 x.c x.c: In function `main': x.c:21: error: Wrong amount of branch edges after unconditional jump 0 x.c:21: internal compiler error: verify_flow_info failed Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. This used to work with 2.95, but failed with 3.0 first. The following slighty simpler code also crashes the compiler, but please don't anyone ask me whether this makes any sense any more: ------------------------------- void jumpaway(int *ptr) { __builtin_longjmp(ptr,1); } int main(void) { __builtin_setjmp(0); jumpaway(0); } -------------------------- http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4382
next reply other threads:[~2002-12-06 23:55 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-06 15:55 bangerth [this message] 2002-12-19 15:26 Janis Johnson
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=20021206235505.4985.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=malekith@pld.org.pl \ --cc=nobody@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).