public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: James Troup <james@nocrew.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/4924: G++ (3.0.2) ICE with -O3 on hppa linux; fixed by -O2 Date: Sat, 01 Dec 2001 16:46:00 -0000 [thread overview] Message-ID: <20011202004602.21056.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c++/4924; it has been noted by GNATS. From: James Troup <james@nocrew.org> To: rodrigc@gcc.gnu.org Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/4924: G++ (3.0.2) ICE with -O3 on hppa linux; fixed by -O2 Date: 02 Dec 2001 00:36:59 +0000 [Am I meant to keep that rather long Cc line?] rodrigc@gcc.gnu.org writes: > Synopsis: G++ (3.0.2) ICE with -O3 on hppa linux; fixed by -O2 > > State-Changed-From-To: open->feedback > State-Changed-By: rodrigc > State-Changed-When: Sat Dec 1 12:54:08 2001 > State-Changed-Why: > I just compiled your testcase with: > gcc version 3.0.3 20011201 (prerelease) under > Redhat Linux 7.1, and did not segfault the > compiler. > > Can you try a newer gcc version and see > if the problem is fixed under hppa Linux? Sorry, I meant to mention that in my report but forgot; I tried to build a newer gcc snapshot for hppa, but it didn't compile. I asked around and was told it was a known problem. I'll try again and see if I can get something newer to build now. -- James
next reply other threads:[~2001-12-02 0:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-01 16:46 James Troup [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-12 20:04 rodrigc 2001-12-01 12:56 rodrigc 2001-12-01 12:54 rodrigc 2001-11-17 0:05 james
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=20011202004602.21056.qmail@sourceware.cygnus.com \ --to=james@nocrew.org \ --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).