This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Fwd: M68K disassembly oddness
- From: Jason Duerstock <jason dot duerstock at gmail dot com>
- To: binutils at sourceware dot org
- Date: Mon, 23 Jan 2017 12:32:20 -0500
- Subject: Fwd: M68K disassembly oddness
- Authentication-results: sourceware.org; auth=none
- References: <CAP5F8cJveBbjpSzvxDwz3wcjyfO9+sqgNfh5bCg_1-Ec0Ua7Cg@mail.gmail.com>
I'm using objdump on some m68k binaries, and I'm seeing some misformatting:
$ m68k-linux-gnu-objdump -D -b binary -m 68040 tmp1.bin
tmp1.bin: file format binary
Disassembly of section .data:
00000000 <.data>:
0: 4ab0 3c00 tstl %a0@(0000000000000000,%d3:l:4)
$ m68k-linux-gnu-objdump -D -b binary -m 68040 tmp2.bin
tmp2.bin: file format binary
Disassembly of section .data:
00000000 <.data>:
0: 4ab0 3c0a tstl %a0@(000000000000000a,%d3:l:4)
In the first example, I think it should just remove the
"0000000000000000,", as it reassembles fine without it. In the second
example, it should at least preface it with "0x", but preferably
display it as "0xa" or "0x0a".
I've tried looking at the code but it's not entirely clear where this
processing happens. Can someone point me in the right direction?
Thanks,
Jason