public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "J. Adam Butts" <butts@cs.wisc.edu> To: rth@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/5704: -O2 causes internal compiler error on alpha Date: Thu, 07 Mar 2002 12:46:00 -0000 [thread overview] Message-ID: <20020307204603.27764.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/5704; it has been noted by GNATS. From: "J. Adam Butts" <butts@cs.wisc.edu> To: rth@gcc.gnu.org, butts@cs.wisc.edu, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rth@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: optimization/5704: -O2 causes internal compiler error on alpha Date: Thu, 7 Mar 2002 14:42:24 -0600 (CST) The latest release version is 3.0.4. By stating that the bug is fixed in 3.1, I assume you're talking about current CVS sources? Do you have any idea how extensive the patch is that fixed this error and whether it has been fixed by 3.0.4? All of my installed software is managed centrally and the support folks are loath to install a new compiler version unless it provably fixes this problem. J. Adam Butts butts@cs.wisc.edu http://www.cs.wisc.edu/~butts On 21 Feb 2002 rth@gcc.gnu.org wrote: > Synopsis: -O2 causes internal compiler error on alpha > > Responsible-Changed-From-To: unassigned->rth > Responsible-Changed-By: rth > Responsible-Changed-When: Wed Feb 20 16:53:57 2002 > Responsible-Changed-Why: > . > State-Changed-From-To: open->feedback > State-Changed-By: rth > State-Changed-When: Wed Feb 20 16:53:57 2002 > State-Changed-Why: > Fixed for gcc 3.1, I think. Leastways I can't reproduce it. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5704 >
next reply other threads:[~2002-03-07 20:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-07 12:46 J. Adam Butts [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-16 5:08 rodrigc 2002-03-07 12:56 Richard Henderson 2002-02-20 17:28 rth 2002-02-15 15:16 butts
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=20020307204603.27764.qmail@sources.redhat.com \ --to=butts@cs.wisc.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=rth@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).