From: Daniel Jacobowitz <drow@false.org>
To: "H. J. Lu" <hjl@lucon.org>
Cc: jbeulich@novell.com, binutils@sources.redhat.com
Subject: Re: Gas is broken for x86-64
Date: Sat, 06 Nov 2004 00:41:00 -0000 [thread overview]
Message-ID: <20041106004136.GA7457@nevyn.them.org> (raw)
In-Reply-To: <20041105231759.GA2855@lucon.org>
On Fri, Nov 05, 2004 at 03:17:59PM -0800, H. J. Lu wrote:
> On Fri, Nov 05, 2004 at 03:04:29PM -0800, H. J. Lu wrote:
> > On Fri, Nov 05, 2004 at 03:00:27PM -0800, H. J. Lu wrote:
> > > On Fri, Nov 05, 2004 at 02:47:58PM -0800, H. J. Lu wrote:
> > > > Hi Jan,
> > > >
> > > > Your i386 opcode change breaks x86-64. I got
> > > >
> > > > [hjl@gnu-64 gas]$ cat /tmp/x.s
> > > > movzb (%rax),%edx
> > > > [hjl@gnu-64 gas]$ ./as-new -o x.o /tmp/x.s
> > > > /tmp/x.s: Assembler messages:
> > > > /tmp/x.s:1: Error: no such instruction: `movzb (%rax),%edx'
> > > >
> > > >
> > >
> > > Your patch
> > >
> > > http://sources.redhat.com/ml/binutils/2004-11/msg00033/binutils-mainline-x86-intel-syntax.patch
> > >
> > > removed movzb. It is wrong.
> >
> > BTW, do you know what other instructions you have removed? We can't
> > remove any of them unless we have a very good reason.
> >
>
> I checked in a patch to restore "movzb":
>
> http://sources.redhat.com/ml/binutils-cvs/2004-11/msg00045.html
Then please add this to the testsuite.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-11-06 0:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 22:48 H. J. Lu
2004-11-05 23:00 ` H. J. Lu
2004-11-05 23:04 ` H. J. Lu
2004-11-05 23:18 ` H. J. Lu
2004-11-06 0:41 ` Daniel Jacobowitz [this message]
2004-11-06 1:18 ` H. J. Lu
2004-11-08 8:20 Jan Beulich
2004-11-08 8:38 ` Alan Modra
2004-11-08 8:55 Jan Beulich
2004-11-08 9:31 ` Alan Modra
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=20041106004136.GA7457@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=jbeulich@novell.com \
/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).