public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: binutils@sourceware.org
Subject: Re: Why aren't we consistent on displacement in x86 	disassembler?
Date: Thu, 26 Apr 2007 15:59:00 -0000	[thread overview]
Message-ID: <20070426155426.GA14771@lucon.org> (raw)
In-Reply-To: <4630E319.76E4.0078.0@novell.com>

On Thu, Apr 26, 2007 at 04:36:25PM +0100, Jan Beulich wrote:
> >We can do one of
> >
> >1. Use decimal on all 8bit displacements and hex on all 16/32bit
> >displacement.
> >2. Use hex on all displacements.
> >
> >Any comments?
> 
> I'd prefer option 2. Jan

I have another idea. We use decimal on all displacements which
can be fitted in 8 bits since -128 is easier to read than
0xffffff80 and is what is in the original assembly code anyway.


H.J.

  reply	other threads:[~2007-04-26 15:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26 14:43 H. J. Lu
2007-04-26 14:54 ` H. J. Lu
2007-04-26 15:54   ` Jan Beulich
2007-04-26 15:59     ` H. J. Lu [this message]
2007-04-26 16:05       ` Jan Beulich
2007-04-26 16:23         ` H. J. Lu
2007-04-26 16:31     ` Alan Modra
2007-04-26 17:19       ` H. J. Lu
2007-04-27  8:40         ` PATCH: PR binutils/4430: We aren't consistent on displacement in x86 disassembler H. J. Lu
2007-04-27 12:40           ` PATCH: Little endian target "binary_little" Kai Tietz
2007-04-27 13:54             ` Alan Modra
2007-04-27 14:54               ` Kai Tietz
2007-04-27 16:26                 ` Alan Modra
2007-04-27 13:39           ` PATCH: PR binutils/4430: We aren't consistent on displacement in x86 disassembler Paul Brook

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=20070426155426.GA14771@lucon.org \
    --to=hjl@lucon.org \
    --cc=binutils@sourceware.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).