public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/4382: [3.2/3.3 regression] __builtin_{set,long}jmp with -O3 can crash the compiler Date: Thu, 19 Dec 2002 15:26:00 -0000 [thread overview] Message-ID: <20021219232600.16962.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/4382; it has been noted by GNATS. From: Janis Johnson <janis187@us.ibm.com> To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, malekith@pld.org.pl Cc: Subject: Re: optimization/4382: [3.2/3.3 regression] __builtin_{set,long}jmp with -O3 can crash the compiler Date: Thu, 19 Dec 2002 15:26:15 -0800 The regression reported in PR optimization/4382 showed up starting with this patch: 2000-12-20 Richard Henderson <rth@redhat.com> * rtl.h (REG_NON_LOCAL_GOTO): New. * rtl.c (reg_note_name): Update. * stmt.c (expand_goto): Emit a REG_NON_LOCAL_GOTO note. * builtins.c (expand_builtin_longjmp): Likewise. * flow.c (make_edges): Check for REG_NON_LOCAL_GOTO and do not emit an edge. I used the original, larger test case provided by the submitter. Output from the compiler with the current mainline is the same as that reported by Wolfgang a couple of weeks ago. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4382
next reply other threads:[~2002-12-19 23:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-19 15:26 Janis Johnson [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-06 15:55 bangerth
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=20021219232600.16962.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --cc=gcc-prs@gcc.gnu.org \ --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).