We've just updated MediaWiki and its underlying software. If anything doesn't look or work quite right, please mention it to us. --RanAS

RTI: Difference between revisions

From SnesLab
Jump to: navigation, search
(how many bytes pulled)
(PBR pulled last)
Line 47: Line 47:
|}
|}


'''RTI''' (ReTurn from Interrupt) is a 65x instruction used to return control from an [[interrupt handler]].  It does this by first pulling the [[status flags]] off of the [[stack]] and then the [[program counter]] too.  In native mode, 4 bytes are pulled.  In emulation mode, 3 bytes are pulled.
'''RTI''' (ReTurn from Interrupt) is a 65x instruction used to return control from an [[interrupt handler]].  It does this by first pulling the [[status flags]] off of the [[stack]] and then the [[program counter]] too.  In native mode, the [[program bank register]] is pulled after that for a total of 4 bytes.  In emulation mode, 3 bytes are pulled.


==== Syntax ====
==== Syntax ====

Revision as of 23:07, 31 July 2024

Basic Info
Addressing Mode Opcode Length Speed
Stack (RTI) 40 1 byte 7 cycles*
Flags Affected
N V M X D I Z C
65c816 native mode N V M X D I Z C
6502 emulation mode N V . . D I Z C

RTI (ReTurn from Interrupt) is a 65x instruction used to return control from an interrupt handler. It does this by first pulling the status flags off of the stack and then the program counter too. In native mode, the program bank register is pulled after that for a total of 4 bytes. In emulation mode, 3 bytes are pulled.

Syntax

RTI
Pitfalls
  • RTI should only be run when the e flag is in the same state as when the interrupt fired
  • RTI cannot even tell whether the interrupt actually occurred or not
  • RTI does not increment the program counter after pulling it like RTS and RTL do
Cycle Skipped

RTI takes one fewer cycle in emulation mode as the program bank register doesn't need to be pulled from the stack.

See Also

External Links