aboutsummaryrefslogtreecommitdiff
path: root/todo.org
diff options
context:
space:
mode:
authorAryadev Chavali <aryadev@aryadevchavali.com>2023-11-03 08:15:21 +0000
committerAryadev Chavali <aryadev@aryadevchavali.com>2023-11-03 08:15:21 +0000
commit6194cb6d2cf5cd501aab0135890a7f3d5c9aa914 (patch)
treeb04cef74a266c16800dba31db4c4c3e62e29d839 /todo.org
parent1d4817eb82f39589f4648af32aa5143263873c39 (diff)
downloadovm-6194cb6d2cf5cd501aab0135890a7f3d5c9aa914.tar.gz
ovm-6194cb6d2cf5cd501aab0135890a7f3d5c9aa914.tar.bz2
ovm-6194cb6d2cf5cd501aab0135890a7f3d5c9aa914.zip
Mark off completed tasks in todo.org
Diffstat (limited to 'todo.org')
-rw-r--r--todo.org7
1 files changed, 4 insertions, 3 deletions
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