aboutsummaryrefslogtreecommitdiff
path: root/todo.org
diff options
context:
space:
mode:
authorAryadev Chavali <aryadev@aryadevchavali.com>2023-11-02 20:31:22 +0000
committerAryadev Chavali <aryadev@aryadevchavali.com>2023-11-02 20:31:22 +0000
commitd5e311c9d44793d269e9b8ee5e8c0fa7a1a25a50 (patch)
tree7bf71c7332453877a432a16adf57e4cf9e48533e /todo.org
parentd12820cd2526c63c34e2a2f393faff6d79f56898 (diff)
downloadovm-d5e311c9d44793d269e9b8ee5e8c0fa7a1a25a50.tar.gz
ovm-d5e311c9d44793d269e9b8ee5e8c0fa7a1a25a50.tar.bz2
ovm-d5e311c9d44793d269e9b8ee5e8c0fa7a1a25a50.zip
Started work on preprocessing jump addresses
Diffstat (limited to 'todo.org')
-rw-r--r--todo.org4
1 files changed, 2 insertions, 2 deletions
diff --git a/todo.org b/todo.org
index c0e2188..8749ef5 100644
--- a/todo.org
+++ b/todo.org
@@ -2,14 +2,14 @@
#+author: Aryadev Chavali
#+date: 2023-11-02
-* TODO Write a label/jump system :ASM:
+* WIP 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.
-* TODO Allow relative addresses in jumps :ASM:
+* WIP 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: