Login
Back to forumSee the full topicGo to last reply

Posted By

SVS
on 2002-10-24
 I mean: if a legal instruction need some (steps) works to complete its process,

maybe a non-standard instruction performs *some* steps and not *some* other. Or maybe some bypass steps (temp storing, or so...). Only if these partial steps have a logical completion, it can be useful (for example LAX load .A and load .X). But if the step sequence is stopped in a not logical point, it can be not-useful or near impossible useful (as the grat parto of not-standard works does).

For example WHEN could you use an instruction that does:
(load .A ORed with zeropage-indirectX-addressed, then store result into indirectY-addressed) ?

Or perhaps you have to write a code *planned* TO USE this instruction (to insert not-deassemblying code, for example).



Back to top


Copyright © Plus/4 World Team, 2001-2024