public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: George Garvey <tmwg-gcc@inxservices.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: Mon, 03 Dec 2001 11:36:00 -0000	[thread overview]
Message-ID: <20011203193603.20260.qmail@sources.redhat.com> (raw)

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

From: George Garvey <tmwg-gcc@inxservices.com>
To: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Cc:  
Subject: Re: c++/4979: g++ 3.0 & 3.1 compile failes with unable to find register to spill
Date: Mon, 3 Dec 2001 09:03:43 -0800

 On Mon, Dec 03, 2001 at 04:39:28PM -0000, rodrigc@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: rodrigc
 > State-Changed-When: Mon Dec  3 08:39:28 2001
 > State-Changed-Why:
 >     Could not reproduce the failure with:
 >     gcc 3.0.2
 >     gcc 3.1 20011201 
 >     
 >     What version is 3.0.99.4?
 
    I modified the 3.1 snapshot version number, so I can keep multiple 3.1
 snapshots on the system at 1 time. So, that's the fourth 3.1 snapshort
 I've tried recently, from 20011201.
    I apologize, but I forgot to say that its -fschedule-insns that
 causes the problem. I thought I did put the command line in the report,
 though I don't see it on the report in GNATS. I suspect that's why 2.95
 worked: it didn't have that flag on the command line.


             reply	other threads:[~2001-12-03 19:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 11:36 George Garvey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-21 11:06 George Garvey
2002-04-21 11:06 Mark Mitchell
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  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=20011203193603.20260.qmail@sources.redhat.com \
    --to=tmwg-gcc@inxservices.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).