thomasabishop/eolas
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Autosave: 2024-04-20 13:00:05

Browse source
This commit is contained in:
thomasabishop 2024-04-20 13:00:05 +01:00
parent 8ed39d3178
commit 75aa6785fa
3 changed files with 6 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

BIN
.zk/notebook.db
View file

Binary file not shown.

0
stack_data_structure.md
View file

11
zk/Stack_memory.md
View file

@ -12,18 +12,19 @@ of programs.
## Stack memory
Similarly to the [[Stacks|stacks]], it works on the basis of LIFO: the last item
put on the stack is the first item to be withdrawn.
Similarly to the [[Stacks|stack data structure]], it works on the basis of LIFO:
the last item put on the stack is the first item to be withdrawn.
Note, this doesn't mean that the data at the memory addresses that comprise the
stack can _only_ be accessed in a LIFO manner. Any item currently on the stack
can be accessed (be read or modified) at any time. LIFO applies when it is is
time to clear memory from the stack: the most recent addition is cleared first.
time to clear memory from the stack: the most recent addition is cleared first
from the top down.
### Stack pointer
A **stack pointer** is used to manage the items in the stack. This value is
stored in a [[processor register]] and its value is the memory address of the
item currently on the top of the stack.
stored in a [[CPU_architecture#registers|register]] and its value is the memory
address of the item currently on the top of the stack.
## Related notes