public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Robert Lipe <robertl@dgii.com>
To: "H.J. Lu" <hjl@lucon.org>, Ian Lance Taylor <ian@cygnus.com>
Cc: 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 13:23:00 -0000	[thread overview]
Message-ID: <19980408152132.36029@dgii.com> (raw)
In-Reply-To: <m0yN0Nt-000597C@ocean.lucon.org>

> >    > 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
> 
> I guess it is ok for short term. If I am correct, as on SCO doesn't
> like it either. My egcs patch should fix gcc.c-torture/compile/980329-1.c
> on SCO too. That is a real bug in egcs. But the current gas doesn't
> catch it. Mine and as on SCO do.

(SCO makes a couple of different operating systems.  I'm commenting 
on OpenServer 5.0.4.)

As luck would have it, I just happen to have handy an egcs build tree
with GNU as wired into it.

(robertl) rjlhome:/play/negcs/gcc
$ ./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
(robertl) rjlhome:/play/negcs/gcc
$ ./xgcc -melf -B./ -O3 /tmp/980329-1.c
/usr/tmp/cca000Yo.s: Assembler messages:
/usr/tmp/cca000Yo.s:76: Error: register does not match opcode suffix
(robertl) rjlhome:/play/negcs/gcc
$ mv as as_
(robertl) rjlhome:/play/negcs/gcc
$ ./xgcc -mcoff -B./ -O3 /tmp/980329-1.c
Assembler: 980329-1.c
        aline 75        : Syntax error
(robertl) rjlhome:/play/negcs/gcc
$ ./xgcc -melf -B./ -O3 /tmp/980329-1.c
/usr/tmp/cca000Z0.s:76:invalid register for instruction: %di in incb

This test case fails to assemble for {COFF,ELF} {GAS,OpenServer as}.

./as in this example is that nasty shell script wrapper I've had hanging
around forever.

The GAS I use is the one from the binutils 2.9 candidates area. I think
there has been one more since.


I don't understand the issue well enough to register an opinion.  I'm
just offering that the behaviour (fatal error) I see from GAS is very
consistent with what we see from OpenServer's as.

-- 
Robert Lipe       http://www.dgii.com/people/robertl       robertl@dgii.com
                  (WEB ADDRESS TEMPORARILY UNAVAILABLE)

  reply	other threads:[~1998-04-08 13:23 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 [this message]
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=19980408152132.36029@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).