public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gabor Greif <gabor@mac.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/9929: [3.3/3.4 regression] Can't find spill register in GENERAL_REGS
Date: Wed, 26 Mar 2003 20:16:00 -0000	[thread overview]
Message-ID: <20030326201601.5739.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/9929; it has been noted by GNATS.

From: Gabor Greif <gabor@mac.com>
To: Steven Bosscher <s.bosscher@student.tudelft.nl>
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
   gcc-prs@gcc.gnu.org, janis187@us.ibm.com, jh@suse.cz
Subject: Re: target/9929: [3.3/3.4 regression] Can't find spill register in GENERAL_REGS
Date: Wed, 26 Mar 2003 21:15:43 +0100

 The patch on mainline seems to work. I did not try gcc3.3.
 
 Thanks to you all for the prompt response,
 
 	Gabor
 
 
 Am Dienstag den, 25. M=E4rz 2003, um 09:25, schrieb Steven Bosscher:
 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-
 > trail&database=3Dgcc&pr=3D9929
 >
 > Hi,
 >
 > Janis, thanks for identifying the patch that caused
 > the PR, I've never seen a patch show up so fast :-)
 >
 > Unfortunately, maybe the patch you identified only
 > uncovers a problem introduced earlier.  PR 10017 is
 > another regression where GCC cannot find a spill
 > register, and that one fails for all GCCs since 3.0.
 > It still fails with Honza's patch applied...
 >
 > Greetz
 > Steven
 >
 


             reply	other threads:[~2003-03-26 20:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 20:16 Gabor Greif [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-03 21:02 jason
2003-03-25  8:37 Steven Bosscher

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=20030326201601.5739.qmail@sources.redhat.com \
    --to=gabor@mac.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).