From 6194cb6d2cf5cd501aab0135890a7f3d5c9aa914 Mon Sep 17 00:00:00 2001 From: Aryadev Chavali Date: Fri, 3 Nov 2023 08:15:21 +0000 Subject: Mark off completed tasks in todo.org --- todo.org | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'todo.org') diff --git a/todo.org b/todo.org index 8749ef5..854fb29 100644 --- a/todo.org +++ b/todo.org @@ -2,17 +2,18 @@ #+author: Aryadev Chavali #+date: 2023-11-02 -* WIP Write a label/jump system :ASM: +* Completed +** DONE Write a label/jump system :ASM: Essentially a user should be able to write arbitrary labels (maybe through ~label x~ or ~x:~ syntax) which can be referred to by ~jump~. It'll purely be on the assembler side as a processing step, where the emitted bytecode purely refers to absolute addresses; the VM should just be dealing with absolute addresses here. -* WIP Allow relative addresses in jumps :ASM: +** DONE Allow relative addresses in jumps :ASM: As requested, a special syntax for relative address jumps. Sometimes it's a bit nicer than a label. -* TODO Calling and returning control flow :VM: :ASM: +** DONE Calling and returning control flow :VM: :ASM: When writing library code we won't know the addresses of where callers are jumping from. However, most library functions want to return control flow back to where the user had called them: we want -- cgit v1.2.3-13-gbd6f