|
MAME x86 disassembler behaviour
#272904 - 01/14/12 01:38 AM
|
|
|
the opcodes
f6 xx (test byte, val)
and
80 &38=38 (cmp byte, val)
show -val when val is 0x80..0xff
While it is technically correct, I find it harder to read.
Is there an option to display using unsigned values, or it requires changing the code?
|
|
|
| drewcifer |
|
One bad Mutha-(shut yo' mouth!)
|
|
|
|
|
Reged: 07/01/04
|
|
Posts: 428
|
|
Loc: Sweden
|
|
|
|
Send PM
|
|
|
Re: MAME x86 disassembler behaviour
[Re: peter ferrie]
#272911 - 01/14/12 03:18 AM
|
|
|
Good question, and thanks for looking at the x86 stuff in MAME!
MAME's debugger is pretty basic, and while it would be super-cool to have numeric value printing options, really all it does right now is call a function in a core's disassembler that sprintfs to a string. And each core's disassembler does it differently. So, to my knowledge, your best bet for now is to just edit the disassembly core to print out what you want it to print out.
It's possible people on MAMEdev share your opinion of how the number should be printed, and a patch that does what you describe may be gladly incorporated into mainstream.
Andrew
> the opcodes
> f6 xx (test byte, val)
> and
> 80 &38=38 (cmp byte, val)
>
> show -val when val is 0x80..0xff
>
> While it is technically correct, I find it harder to read.
> Is there an option to display using unsigned values, or it requires changing the
> code?
|
|
|
|
Previous 
Index 
Next 
Threaded 
MAME x86 disassembler behaviour
Reply
[Re: 