From 913202c8165cc121c6add6da6c2937cb5f6fc276 Mon Sep 17 00:00:00 2001 From: yatesal Date: Sun, 20 May 2018 23:24:38 -0700 Subject: [PATCH] Included an image to help understand the stack. --- Basic-Assembly-tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Basic-Assembly-tutorial.md b/Basic-Assembly-tutorial.md index a76f504..b3cf723 100644 --- a/Basic-Assembly-tutorial.md +++ b/Basic-Assembly-tutorial.md @@ -441,6 +441,6 @@ 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](link to picture) +![Visual representation of the stack](https://user-images.githubusercontent.com/25143248/40293017-a0faff04-5c83-11e8-8a84-75ea058b8655.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**. \ No newline at end of file