public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: cgd@broadcom.com To: rsandifo@sources.redhat.com Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/9301: [regression] [mips-linux] gcc 3.2.1 SEGV in try_forward_edges Date: Mon, 31 Mar 2003 20:26:00 -0000 [thread overview] Message-ID: <20030331201600.3872.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/9301; it has been noted by GNATS. From: cgd@broadcom.com To: rsandifo@sources.redhat.com Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org, rsandifo@sources.redhat.com Subject: Re: optimization/9301: [regression] [mips-linux] gcc 3.2.1 SEGV in try_forward_edges Date: 31 Mar 2003 12:07:23 -0800 At 31 Mar 2003 19:18:26 -0000, rsandifo@sources.redhat.com wrote: > Do you know if this is still a problem? > > I can't reproduce it with the head of gcc-3_2-branch using > an i686-pc-linux-gnu cross mipsel-linux-gnu compiler (tried > -EB -O2 as well as -O2). I can't reproduce with gcc 3.3 > or trunk either. > > I'll try a native compiler as well as a pristine 3.2.1 build. I just tried 3.2.2 (plus local mods) and it seems to work fine. the patch: > 2003-02-03 Eric Botcazou <ebotcazou@libertysurf.fr> > > PR ice-on-legal-code/9493 > * cfgcleanup.c (try_forward_edges): Check for null insn. might have done it; i dunno i didn't analyze it further. i looked at a .o that resulted from compiling the file, it looked OK (as far as I could tell, on a quick read). Now that it works, IMO this test should be thrown into the testsuite as a compilation test. chris
next reply other threads:[~2003-03-31 20:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-31 20:26 cgd [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-31 21:10 rsandifo 2003-03-31 19:30 rsandifo
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=20030331201600.3872.qmail@sources.redhat.com \ --to=cgd@broadcom.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=rsandifo@sources.redhat.com \ /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).