From: Jeffrey A Law <law@cygnus.com>
To: Bernd Schmidt <crux@ohara.Informatik.RWTH-Aachen.DE>
Cc: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>, egcs@cygnus.com
Subject: Re: next glibc showstopper
Date: Sat, 06 Dec 1997 07:50:00 -0000 [thread overview]
Message-ID: <27834.881423594@hurl.cygnus.com> (raw)
In-Reply-To: <Pine.SOL.3.90.971203141551.10301F-100000@ohara.informatik.rwth-aachen.de>
In message <Pine.SOL.3.90.971203141551.10301F-100000@ohara.informatik.rwth-aa
chen.de>you write:
> > This indeed should have been done in i386.[ch].
> >
> > Can you show me the exact RTL so we can figure out where it should
> > be changed?
>
> I've figured it out. It turned out to be caused by a piece of code from
> Intel's pentium patches that shouldn't have gotten in there. Removing this
> code fixes the problem.
>
> Bernd
>
> * i386.c (notice_update_cc): Remove bogus pentium GCC code.
Thanks. I've installed this patch into egcs.
jeff
next prev parent reply other threads:[~1997-12-06 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9712012221.AA15274@vlsi1.ultra.nyu.edu>
1997-12-03 5:46 ` Bernd Schmidt
1997-12-06 7:50 ` Jeffrey A Law [this message]
1997-11-21 21:50 Ulrich Drepper
1997-12-01 5:20 ` Bernd Schmidt
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=27834.881423594@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=crux@ohara.Informatik.RWTH-Aachen.DE \
--cc=egcs@cygnus.com \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).