We've just updated MediaWiki and its underlying software. If anything doesn't look or work quite right, please mention it to us. --RanAS
Stack: Difference between revisions
From SnesLab
(top of stack ref) |
(LIFO) |
||
| Line 1: | Line 1: | ||
The '''Stack''' is a buffer which remembers the state of subroutines that are currently executing. | The '''Stack''' is a LIFO (last-in, first-out) buffer which remembers the state of subroutines that are currently executing. | ||
On the [[65c816]], the stack is always in [[bank]] zero.<sup>[3]</sup> It can be thousands of bytes deep.<sup>[1]</sup> | On the [[65c816]], the stack is always in [[bank]] zero.<sup>[3]</sup> It can be thousands of bytes deep.<sup>[1]</sup> | ||
Revision as of 19:48, 12 November 2024
The Stack is a LIFO (last-in, first-out) buffer which remembers the state of subroutines that are currently executing.
On the 65c816, the stack is always in bank zero.[3] It can be thousands of bytes deep.[1]
In emulation mode it wraps within page one.[2]
The stack grows towards zero, but the most recently pushed byte is nontheless called the top of the stack.[4] These instructions push things to the stack:
PL* instructions take one cycle more than their PH* counterparts. These instructions pull things from the stack:
Note the lack of PLK. PHS and PLS similarly do not exist, nor do any instructions performing the inverse of PEA, PEI, or PER.
See Also
References
- Wilson, Garth. https://wilsonminesco.com/816myths
- Clark, Bruce. http://www.6502.org/tutorials/65c816opcodes.html#5.1.1
- section 2.11 of 65c816 datasheet: https://www.westerndesigncenter.com/wdc/documentation/w65c816s.pdf
- Eyes & Lichty, page 33