public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Roger Sayle <roger@eyesopen.com>
To: Andreas Jaeger <aj@suse.de>
Cc: Graham Stott <graham.stott@btinternet.com>, <gcc@gcc.gnu.org>,
	<gcc-patches@gcc.gnu.org>
Subject: Re: gcc bootstrap broken on i686-linux-gnu
Date: Thu, 01 Aug 2002 09:04:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0208010944220.26052-100000@www.eyesopen.com> (raw)
In-Reply-To: <hoit2upr2n.fsf@gee.suse.de>


On Thu, 1 Aug 2002, Andreas Jaeger wrote:
> Graham Stott <graham.stott@btinternet.com> writes:
> > I think Roger's patch just tickles a problem in the x86 backend.
> >
> > register_operand may also match SUBREG which isn't valid for the
> > REGNO macro hence the abort when enable checking is enabled.
> >
> > I think the uses of FP_REGNO_P (REGNO (...)) should be FP_REG_P (...)
> > which checks it's operand is a REG before checking the REGNO.
> >
> > I've got such a patch in the works.
>
> The bootstrap problem still exists for me.  I haven't tested Graham's
> patch but I've noticed that it's unreviewed and I expect it to solve
> the problem.  Can somebody review it, please?

Make that two requests for someone to review this patch.  The patch
itself is at http://gcc.gnu.org/ml/gcc-patches/2002-07/msg01753.html

Many thanks in advance,

Roger
--

  reply	other threads:[~2002-08-01 16:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-29 10:42 Andreas Jaeger
2002-07-29 16:46 ` Roger Sayle
2002-07-29 20:45   ` Andreas Jaeger
2002-07-30  2:09     ` Graham Stott
2002-07-30  3:31       ` Roger Sayle
2002-08-01  7:54       ` Andreas Jaeger
2002-08-01  9:04         ` Roger Sayle [this message]
2002-07-30  3:23     ` Roger Sayle
2002-07-29 21:30 John David Anglin
2002-07-30  3:30 ` Roger Sayle

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=Pine.LNX.4.33.0208010944220.26052-100000@www.eyesopen.com \
    --to=roger@eyesopen.com \
    --cc=aj@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=graham.stott@btinternet.com \
    /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).