From ce015ca2949b4db2babd03fe387b8b1999a8f60a Mon Sep 17 00:00:00 2001 From: nitro2k01 Date: Mon, 26 Dec 2022 07:18:09 +0100 Subject: [PATCH] Fixed typo --- double-halt-cancel/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/double-halt-cancel/README.md b/double-halt-cancel/README.md index 4cdb7b9..57ce9c5 100644 --- a/double-halt-cancel/README.md +++ b/double-halt-cancel/README.md @@ -50,7 +50,7 @@ In this example, the `rst $08` instruction will not push `$0002` to the stack as So, we can finally see what the `halt` bug actually is: it's an inhibition of the automatic incrementation of PC, meaning in this case that the previous value of `PC` would be pushed to the stack. -[^1]: It might seem like a stretch that a call to a `rst` vector would not return. However, a fairly common pattern is to use an `rst` for jump tables, where the return address is `pop`ped from the stack and used as the base address for the jump table immediately following the `rst` instruction. Doing this after a `halt` instruction is likely, though. +[^1]: It might seem like a stretch that a call to a `rst` vector would not return. However, a fairly common pattern is to use an `rst` for jump tables, where the return address is `pop`ped from the stack and used as the base address for the jump table immediately following the `rst` instruction. Doing this after a `halt` instruction is unlikely, though. ### The double `halt` bug