Difference between revisions of "NOP"
(→mention interruptibility as another good reason for NOPping) |
|||
Line 7: | Line 7: | ||
<tr><td>Opcode Range</td><td>$0034-$0035</td></tr> | <tr><td>Opcode Range</td><td>$0034-$0035</td></tr> | ||
</table><br/> | </table><br/> | ||
− | The No Operation (NOP) instruction performs no function. | + | The No Operation (NOP) instruction performs no function. Programs use NOPs as a time-killer for synchronization purposes. Programs also use NOPs to break up long sequences of non-interruptible instructions in order to allow the STIC to interrupt the CPU or request the bus. The opcode format is as follows.<br/> |
0000:0000:0011:010x<br/> | 0000:0000:0011:010x<br/> | ||
where: | where: | ||
x is ignored | x is ignored |
Revision as of 22:43, 11 January 2005
Instruction Name | No Operation |
Mnemonic | NOP |
CP1610 Clock Cycles | 6 |
Interruptible | Yes |
Opcode Range | $0034-$0035 |
The No Operation (NOP) instruction performs no function. Programs use NOPs as a time-killer for synchronization purposes. Programs also use NOPs to break up long sequences of non-interruptible instructions in order to allow the STIC to interrupt the CPU or request the bus. The opcode format is as follows.
0000:0000:0011:010x
where: x is ignored