public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/4979: g++ 3.0 & 3.1 compile failes with unable to find register to spill
Date: Sun, 21 Apr 2002 11:06:00 -0000	[thread overview]
Message-ID: <20020421180601.8116.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/4979; it has been noted by GNATS.

From: Mark Mitchell <mark@codesourcery.com>
To: George Garvey <tmwg-gcc@inxservices.com>,
   "mmitchel@gcc.gnu.org" <mmitchel@gcc.gnu.org>,
   "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>,
   "gcc-prs@gcc.gnu.org" <gcc-prs@gcc.gnu.org>,
   "nobody@gcc.gnu.org" <nobody@gcc.gnu.org>,
   "gcc-gnats@gcc.gnu.org" <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: c++/4979: g++ 3.0 & 3.1 compile failes with unable to find
 register to spill
Date: Sun, 21 Apr 2002 10:57:55 -0700

 --On Sunday, April 21, 2002 10:55:59 AM -0700 George Garvey 
 <tmwg-gcc@inxservices.com> wrote:
 
 > On Sat, Apr 20, 2002 at 09:02:44PM -0000, mmitchel@gcc.gnu.org wrote:
 >> Synopsis: g++ 3.0 & 3.1 compile failes with unable to find register to
 >> spill
 >>
 >> State-Changed-From-To: open->feedback
 >> State-Changed-By: mmitchel
 >> State-Changed-When: Sat Apr 20 14:02:44 2002
 >> State-Changed-Why:
 >>     There's no test case that shows the bug at this point.
 >>
 >> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=g
 >> cc&pr=4979
 >>
 >
 >    I have none left either, using CVS from last night.
 >    Unfortunately, another ICE has been exposed:
 
 OK, we'll close this one.
 
 >    Would you like this as a new PR?
 
 Yes, please.
 
 --
 Mark Mitchell                   mark@codesourcery.com
 CodeSourcery, LLC               http://www.codesourcery.com
 


             reply	other threads:[~2002-04-21 18:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-21 11:06 Mark Mitchell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-21 11:06 George Garvey
2002-04-21 11:00 mmitchel
2002-04-20 14:02 mmitchel
2002-04-14 11:06 Jason Merrill
2002-04-09  6:05 jason
2002-04-09  5:56 George Garvey
2002-04-09  5:36 Jason Merrill
2002-04-08 17:08 jason
2001-12-21  9:16 Reichelt
2001-12-03 11:46 rodrigc
2001-12-03 11:40 rodrigc
2001-12-03 11:36 George Garvey
2001-12-03  8:46 rodrigc
2001-12-03  8:39 rodrigc

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=20020421180601.8116.qmail@sources.redhat.com \
    --to=mark@codesourcery.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: link
Be 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).