public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Robert Lipe <robertl@dgii.com>
To: Ian Lance Taylor <ian@cygnus.com>
Cc: hjl@lucon.org, schmid@ltoi.iap.physik.tu-darmstadt.de,
	gas2@cygnus.com, egcs@cygnus.com
Subject: Re: binutils 2.9 is broken on x86
Date: Wed, 08 Apr 1998 14:09:00 -0000	[thread overview]
Message-ID: <19980408160936.24054@dgii.com> (raw)
In-Reply-To: <199804082036.QAA02362@subrogation.cygnus.com>

>    $ ./xgcc -mcoff -B./ -O3 /tmp/980329-1.c
>    /usr/tmp/cca000Yh.s: Assembler messages:
>    /usr/tmp/cca000Yh.s:75: Error: register does not match opcode suffix
> 
>    The GAS I use is the one from the binutils 2.9 candidates area. I think
> 
> Whoops, you're right.  I was confused.  gas does catch this particular
> error, and has done so since day one.  I was mistakenly thinking that
> something else was going on here.

egcs emits something bad, but gas and sco as both correctly vomit on it.
H.J. has submitted a patch to fix the egcs problem.

So in all this hysteria, there is nothing broken that we didn't already
know about and we can all feel good about each piece of software
involved, right?

Case closed, or is there another problem here?

RJL

      reply	other threads:[~1998-04-08 14:09 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
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 [this message]

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=19980408160936.24054@dgii.com \
    --to=robertl@dgii.com \
    --cc=egcs@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=hjl@lucon.org \
    --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).