public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: cgd@broadcom.com To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/9301: mips-linux gcc 3.2.1 SEGV in try_forward_edges Date: Tue, 21 Jan 2003 19:56:00 -0000 [thread overview] Message-ID: <20030121195601.27838.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: gcc-gnats@gcc.gnu.org Cc: gcc-bugs@gcc.gnu.org Subject: Re: optimization/9301: mips-linux gcc 3.2.1 SEGV in try_forward_edges Date: 21 Jan 2003 11:52:06 -0800 At Mon, 13 Jan 2003 23:46:29 +0000 (UTC), cgd@broadcom.com wrote: > >Number: 9301 > 3.2.1 also seems to have the problem on embedded mips targets > (e.g. mipsisa64sb1 8-), but I did not try that > configuration with an unmodified compiler. FYI, i tried the same test with some older versions of GCC, slightly modified from stock sources as well (same mods as in the 3.2.1 mentioned above, which shouldn't affect this), and * "gcc version 3.0.3 with SiByte modifications" worked fine. (same for 3.0.4) * "gcc version 3.1.1 with SiByte modifications" also crashed. So, this seems to be a regression from previous releases (at least 3.0.x). I'm can provide the diffs against unmodified gcc from any of those "with SiByte modifications" versions to the sources, if people want them, but really, they're not the problem. 8-) cgd
next reply other threads:[~2003-01-21 19:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-21 19:56 cgd [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-13 23:56 cgd 2003-01-13 23:46 cgd
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=20030121195601.27838.qmail@sources.redhat.com \ --to=cgd@broadcom.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).