Re: [hatari-devel] 68020 addressing modes not correctly disassembled |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
>> As you said, it would be highly confusing to see 68020 opcodes when
>
>> trying to crack a games's protection, while they would result in various
>
>> exception when running in 68000 mode.
>
>
>
> You could mark them as 020+ when in 68000 mode, by a comment or similar.
> The disassembler does not only disasm the current instruction but also
> any range you specify in the command, and then it might be helpful to
> understand the code when seeing the actual instruction.
>
>
>
> But thats only my opinion, and surely won't happen too often ;)
UAE disassembler writes instructions in square brackets that are not
supported (=would generate illegal instruction or F-line) by current CPU
but are supported by some other model.
Unfortunately some 68020+ instructions are technically valid under
68000/010 but work differently, mainly any instructions that use 68020+
new addressing modes. 68000/010 won't generate any exceptions and
executes it as (x,pc/an,dn.x) addressing mode. Some protection code
probably uses these variants. These are marked with "(68020+)" in
disassembler output.