simon987/Much-Assembly-Required
1
0
Fork 0
mirror of https://github.com/simon987/Much-Assembly-Required.git synced 2025-04-19 18:46:43 +00:00
Code Issues Projects Releases Wiki Activity

Updated diagram explaining the stack data structure.

yatesal 2018-05-21 20:02:54 -07:00
parent 913202c816
commit 839a22481d
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Basic-Assembly-tutorial.md

@ -441,6 +441,7 @@ To understand this example, we must first understand what is the **stack**. The
We use the term *push* when we add a piece of data on top of the stack and *pop* when we remove a piece of data from the stack.
Visual representation of the stack:
![Visual representation of the stack](https://user-images.githubusercontent.com/25143248/40293017-a0faff04-5c83-11e8-8a84-75ea058b8655.png)
![Visual representation of the stack](https://user-images.githubusercontent.com/25143248/40339650-38288bb0-5d30-11e8-826f-d0b924b01192.png)
We can notice that this implementation of the stack is actually upside-down compared to a real-world stack of items: the stack grows downwards in memory, towards lower addresses. The important thing to remember is that the bottom of the stack is at a fixed address and that the top of the stack changes when an item is *pushed* on the stack or *popped* out. In the game's CPU, the **stack pointer** (SP) register always points to the top of the stack and the **base pointer** always points to the base of the current **stack frame**.