bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/4430] New: We aren't consistent on displacement in x86 dis


From: hjl at lucon dot org
Subject: [Bug binutils/4430] New: We aren't consistent on displacement in x86 disassembler
Date: 26 Apr 2007 14:00:12 -0000

X-Bugzilla-Reason: CC

We aren't consistent in the format we use on displacement:

----
static void
print_operand_value (char *buf, int hex, bfd_vma disp)
...
static void
OP_E (int bytemode, int sizeflag)
{
...
            print_operand_value (scratchbuf, !riprel, disp);
...
              print_operand_value (scratchbuf, modrm.mod != 1, disp);
...
              print_operand_value (scratchbuf, 1, disp);
...
            print_operand_value (scratchbuf, 0, disp);
...
              print_operand_value (scratchbuf, modrm.mod != 1, disp);
...
          print_operand_value (scratchbuf, 1, disp & 0xffff);
}
----

That is we use hex or decimal for displacement, depending on Intel
mode, RIP relative, modrm.mod != 1 and 16bit address mode. It is
confusing.

-- 
           Summary: We aren't consistent on displacement in x86 disassembler
           Product: binutils
           Version: 2.18 (HEAD)
            Status: NEW
          Severity: normal
          Priority: P2
         Component: binutils
        AssignedTo: unassigned at sources dot redhat dot com
        ReportedBy: hjl at lucon dot org
                CC: bug-binutils at gnu dot org
GCC target triplet: i686-pc-linux-gnu


http://sourceware.org/bugzilla/show_bug.cgi?id=4430

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]