diff options
author | Aryadev Chavali <aryadev@aryadevchavali.com> | 2024-04-09 15:00:59 +0630 |
---|---|---|
committer | Aryadev Chavali <aryadev@aryadevchavali.com> | 2024-04-09 15:10:26 +0630 |
commit | 6df6dce1531a65b887963cb0fc19f2f976b21f8b (patch) | |
tree | 93c7ccc6946d425a9c9ccdb171e73f0ce40de295 | |
parent | 9250a2a8383116a23f77ee6928ad64b44ab3a289 (diff) | |
download | ovm-6df6dce1531a65b887963cb0fc19f2f976b21f8b.tar.gz ovm-6df6dce1531a65b887963cb0fc19f2f976b21f8b.tar.bz2 ovm-6df6dce1531a65b887963cb0fc19f2f976b21f8b.zip |
Added todo to force an endian convention
I've flip flopped a bit on this but I believe the virtual machine
bytecode format must have a convention on endianness. This is because
of the issue stated in the TODO which may very well happen.
-rw-r--r-- | todo.org | 18 |
1 files changed, 18 insertions, 0 deletions
@@ -15,6 +15,24 @@ *** TODO VM [0%] **** TODO vm/runtime.h ** TODO Specification +* TODO Rigid endian :LIB: +Say a program is compiled on a little endian machine. The resultant +bytecode file, as a result of using C's internal functions, will use +little endian. + +This file, when distributed to other computers, will not work on those +that use big endian. + +This is a massive problem; I would like bytecode compiled on one +computer to work on any other one. Therefore we have to enforce big +endian. This refactor is limited to only LIB as a result of only the +~convert_*~ functions being used in the runtime to convert between +byte buffers (usually read from the bytecode file directly or from +memory to use in the stack). + +2024-04-09: Found the ~hto_e~ functions under =endian.h= that provide +both way host to specific endian conversion of shorts, half words and +words. This will make it super simple to just convert. * TODO Preprocessing directives :ASM: Like in FASM or NASM where we can give certain helpful instructions to the assembler. I'd use the ~%~ symbol to designate preprocessor |