This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PATCH: PR binutils/4430: We aren't consistent on displacement in x86 disassembler

From: Paul Brook <paul at codesourcery dot com>
To: binutils at sourceware dot org
Cc: "H. J. Lu" <hjl at lucon dot org>, Jan Beulich <jbeulich at novell dot com>
Date: Fri, 27 Apr 2007 13:40:33 +0100
Subject: Re: PATCH: PR binutils/4430: We aren't consistent on displacement in x86 disassembler
References: <20070426135749.GA9666@lucon.org> <20070426163058.GA15122@lucon.org> <20070427033347.GA17560@lucon.org>

> in 64bit mode, it still displays
>
> 0:   8b 1c 25 00 00 00 80    mov    0xffffffff80000000,%ebx
>
> Should I make it signed like
>
> 0:   8b 1c 25 00 00 00 80    mov    -0x80000000,%ebx
>
> Will it be confusing to people?

The latter would confuse me.
IMHO hex values should always be unsigned.

However this is a 32-bit mov. Why not display it as a 32-bit hex value?

Paul

References:
- Why aren't we consistent on displacement in x86 disassembler?
  - From: H. J. Lu
- Re: Why aren't we consistent on displacement in x86 disassembler?
  - From: H. J. Lu
- PATCH: PR binutils/4430: We aren't consistent on displacement in x86 disassembler
  - From: H. J. Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]