Quote:
Originally Posted by copse
Take this line from Tunnels and Trolls:
Code:
0x6683A: 0xFF3C: 1111[111]100[111][100] cpSAVE 7, Imm
Imm is actually an invalid effective addressing mode for the cpSAVE instruction, so as I understand it should cause an F-Line thingy. I think Resource disassembles these sorts of invalid instructions as "fRestore ?????" or even sometimes "AFLINE something".
Anyone have any insight into the best way to handle these invalid instructions? |
Unrecognized instructions that are not relocations should generate a dc.size like this:
dc.w $ff3c
This will reassemble correctly and can be viewed by a 68k assembly programmer as being f-line if it's determined to be code. If you add x68000 function calls later, this will probably change to being some kind of an OS function name but would probably require an external include/macro file to translate it to what I have above. A dc.w is self contained and easier for an assembler but a function name would be easier for a programmer.