diff options
author | Aryadev Chavali <aryadev@aryadevchavali.com> | 2023-11-03 08:14:47 +0000 |
---|---|---|
committer | Aryadev Chavali <aryadev@aryadevchavali.com> | 2023-11-03 08:14:47 +0000 |
commit | 1d4817eb82f39589f4648af32aa5143263873c39 (patch) | |
tree | 77980f4afc8e09e754cbe9342f606b9598ebd08a | |
parent | 134c06a6fe1c319ae295d5054387b23143215e8e (diff) | |
download | ovm-1d4817eb82f39589f4648af32aa5143263873c39.tar.gz ovm-1d4817eb82f39589f4648af32aa5143263873c39.tar.bz2 ovm-1d4817eb82f39589f4648af32aa5143263873c39.zip |
Started work on spec for data storage types in VM
-rw-r--r-- | spec.org | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -36,6 +36,17 @@ others. Bytecode files are byte sequence which encode instructions for the virtual machine. Any instruction (even with an operand) has one and only one byte sequence associated with it. +* TODO Storage +Two types of storage: ++ Data stack which all core VM routines manipulate and work on (FIFO) ++ Register space which is generally reserved for user space code + i.e. other than ~mov~ no other core VM routine manipulates the + registers +* TODO Assembler conventions +The standard library is allowed to use the first 8 words (64 bytes) of +register space without regard to user applications, so it's +recommended to use register space from the 9th (72nd bit) word onwards +for user applications if standard library is to be used. * Footnotes [fn:2] ~NOOP~, ~HALT~, ~MDELETE~, ~MSIZE~, ~JUMP_*~ |