From: hjl@lucon.org (H.J. Lu)
To: alan@spri.levels.unisa.edu.au (Alan Modra)
Cc: mikeg@weiden.de, gas2@cygnus.com, egcs@cygnus.com, gcc2@cygnus.com
Subject: Re: gcc generates invalid i386 fmulp
Date: Tue, 14 Apr 1998 08:19:00 -0000 [thread overview]
Message-ID: <m0yP7Uc-00058vC@ocean.lucon.org> (raw)
In-Reply-To: <199804131501.AAA05109@mullet.Levels.UniSA.Edu.Au>
>
> Hello all,
> I've been doing a little work on gas for i386, tidying up a few
> things and adding reasonably strict operand/suffix checking. The new
> gas has already found a couple of errors in the linux kernel asm, one
> in glibc1, and a problem with gcc.
>
> For anyone who's interested, the gas patches can be found at
> ftp://mullet.levels.unisa.edu.au/private/teabag/gas-980407-alan.diff.gz
> They should apply to binutils-2.9 without problems too.
>
> The gcc problem (found by mikeg@weiden.de (Michael L. Galbraith)),
> when compiling glibc2 is that gcc will generate instructions like
> `fsubp %st(1),%st'
>
Can you show me a small test case please? It is very tricky. Here are
the ChangeLog entries:
Mon Apr 14 14:56:58 1997 Ian Lance Taylor <ian@cygnus.com>
* i386.h: Change the opcodes for fsubp, fsubrp, fdivp, and fdivrp
with no arguments to match that generated by the UnixWare
assembler.
Sat Apr 5 13:14:05 1997 Ian Lance Taylor <ian@cygnus.com>
* i386.h: Revert last patch for the NON_BROKEN_OPCODES cases.
Fri Apr 4 14:02:32 1997 Ian Lance Taylor <ian@cygnus.com>
* i386.h: Correct opcode values for fsubp, fsubrp, fdivp, and
fdivrp.
It is very different from Intel and very confusing. But changing it
will break many things.
Thanks.
H.J.
next prev parent reply other threads:[~1998-04-14 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-14 0:15 Alan Modra
1998-04-14 8:19 ` H.J. Lu [this message]
1998-04-14 16:45 ` Alan Modra
1998-04-14 20:18 ` Michael L. Galbraith
1998-04-14 20:30 ` H.J. Lu
1998-04-14 21:35 ` Michael L. Galbraith
1998-04-14 20:44 ` H.J. Lu
1998-04-15 7:18 ` Alan Modra
1998-04-15 9:01 ` Robert Lipe
1998-04-15 10:05 ` Ulrich Drepper
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=m0yP7Uc-00058vC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=alan@spri.levels.unisa.edu.au \
--cc=egcs@cygnus.com \
--cc=gas2@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=mikeg@weiden.de \
/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).