public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: hjl@lucon.org (H.J. Lu)
To: ian@cygnus.com (Ian Lance Taylor)
Cc: schmid@ltoi.iap.physik.tu-darmstadt.de, egcs@cygnus.com, gas2@cygnus.com
Subject: Re: binutils 2.9 is broken on x86
Date: Wed, 08 Apr 1998 11:15:00 -0000	[thread overview]
Message-ID: <m0yMzNm-00058tC@ocean.lucon.org> (raw)
In-Reply-To: <199804081805.OAA24674@subrogation.cygnus.com>

> 
>    From: hjl@lucon.org (H.J. Lu)
>    Date: Wed, 8 Apr 1998 11:01:08 -0700 (PDT)
> 
>    > These are the testsuite results for egcs-2.91.22 on the
>    > i386-pc-linux-gnulibc1 system. I had to add --disable-nls to configure
>    > to compile egcs. What about making --disable-nls a default option for
>    > the texinfo configure?
>    > 
>    > Peter Schmid
>    > 
>    > gcc:
>    > gcc.sum:FAIL: gcc.c-torture/compile/980329-1.c,  -O2 
>    > /tmp/cca17739.s: Assembler messages:
>    > /tmp/cca17739.s:75: Error: register does not match opcode suffix
> 
> This is an error which H.J. added to his version of the binutils.  It
> is not yet in the GNU binutils.
> 
>    binutils 2.9 is broken on x86. It silently turns
> 
>    incb %di
> 
>    into
> 
>    incl   %edi
> 
>    Although my binutils chokes on it, however it didn't generate
>    bogus opcode. I will make binutils 2.8.1.0.30 to fix it. In
>    the meantime, please don't go back to old binutils.
> 
>    Ian, please don't make 2.9 as is. It turns out my worry comes
>    true. My x86 patch seems quite useful.
> 
> Although H.J. doesn't mention it, gas has behaved this way for many
> years.
> 
> I do not plan to delay the 2.9 release to change this behaviour.  The
> potential bad consequences of adding errors, and thus failing to
> assemble existing code, are serious.  Turning `incb %di' into `incl
> %edi' will almost always be harmless.

I am not sure about it. There is no "incb %di" in Intel x86
instrucntion set. It should be either "incw %di" or "incl %edi".
I am not sure if they are the same. In that case, I don't know
why egcs emits "incb %di". It doesn't look right.


H.J.
-- 
H.J. Lu (hjl@gnu.org)

  reply	other threads:[~1998-04-08 11:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.A32.3.95.980408111418.23610A-100000@ltoi.iap.physik.tu-darmstadt.de>
1998-04-08 11:01 ` H.J. Lu
1998-04-08 11:05   ` Ian Lance Taylor
1998-04-08 11:15     ` H.J. Lu [this message]
1998-04-08 12:19     ` H.J. Lu
1998-04-08 13:23       ` Robert Lipe
1998-04-08 13:30         ` H.J. Lu
1998-04-08 13:42         ` Ian Lance Taylor
1998-04-08 14:09           ` Robert Lipe

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=m0yMzNm-00058tC@ocean.lucon.org \
    --to=hjl@lucon.org \
    --cc=egcs@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=ian@cygnus.com \
    --cc=schmid@ltoi.iap.physik.tu-darmstadt.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).