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

> 
> 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
> 

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.

Thanks.

H.J.

       reply	other threads:[~1998-04-08 11:01 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 [this message]
1998-04-08 11:05   ` Ian Lance Taylor
1998-04-08 11:15     ` H.J. Lu
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=m0yMz9o-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).