From: Bernd Schmidt <crux@ohara.Informatik.RWTH-Aachen.DE>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: egcs@cygnus.com
Subject: Re: next glibc showstopper
Date: Wed, 03 Dec 1997 05:46:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.90.971203141551.10301F-100000@ohara.informatik.rwth-aachen.de> (raw)
In-Reply-To: <9712012221.AA15274@vlsi1.ultra.nyu.edu>
> 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.
*** ./config/i386/i386.c.orig-1 Tue Dec 2 20:08:51 1997
--- ./config/i386/i386.c Tue Dec 2 20:12:18 1997
*************** notice_update_cc (exp)
*** 3542,3556 ****
if (SET_DEST (exp) == pc_rtx)
return;
- #ifdef IS_STACK_MODE
- /* Moving into a memory of stack_mode may have been moved
- in between the use and set of cc0 by loop_spl(). So
- old value of cc.status must be retained */
- if (GET_CODE(SET_DEST(exp)) == MEM
- && IS_STACK_MODE (GET_MODE (SET_DEST (exp))))
- return;
- #endif
-
/* Moving register or memory into a register:
it doesn't alter the cc's, but it might invalidate
the RTX's which we remember the cc's came from.
--- 3542,3547 ----
next parent reply other threads:[~1997-12-03 5:46 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 [this message]
1997-12-06 7:50 ` Jeffrey A Law
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=Pine.SOL.3.90.971203141551.10301F-100000@ohara.informatik.rwth-aachen.de \
--to=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).