Age | Commit message (Collapse) | Author | |
---|---|---|---|
2023-10-15 | Main now loads a stack allocated byte array for VM stack | Aryadev Chavali | |
2023-10-15 | Added a routine to load a pointer as stack memory | Aryadev Chavali | |
2023-10-15 | Changed stack data to be a pointer | Aryadev Chavali | |
I wouldn't really want this to be malloc'd per se, you could make a byte array on the stack then pass it into the VM? | |||
2023-10-15 | Split off general types and structures into separate header | Aryadev Chavali | |
2023-10-15 | Changed stack.pointer->stack.ptr | Aryadev Chavali | |
2023-10-15 | Added floats (64 bit floating point) push and pop routines | Aryadev Chavali | |
Not machine independent, uses the underlying memcpy routine. | |||
2023-10-15 | Force big endian when pushing words | Aryadev Chavali | |
This ensures that if one wanted to pop a word byte by byte, they'd go from least to most significance. Machine independent so that's nice. | |||
2023-10-15 | Add macro for size of a word | Aryadev Chavali | |
Smaller number of changes necessary to change types. | |||
2023-10-15 | Added macro constructors for union types | Aryadev Chavali | |
2023-10-15 | Implemented functions to pop a byte and a word | Aryadev Chavali | |
2023-10-15 | Implemented a union type to make vm_push_* routines uniform | Aryadev Chavali | |
Function dispatch | |||
2023-10-15 | Added functions to push a byte and a word | Aryadev Chavali | |
Maybe I should make a union for the type, so I can dispatch via function pointers? | |||
2023-10-15 | Defined a simple virtual machine data structure | Aryadev Chavali | |
Currently just contains a "stack". | |||
2023-10-15 | Added some type aliases | Aryadev Chavali | |
Nicer to refer to a byte as "byte" rather than "uint8_t" | |||
2023-10-15 | Added a README | Aryadev Chavali | |
2023-10-15 | Remove unit tests from github workflow | Aryadev Chavali | |
We don't *have* unit tests lol. | |||
2023-10-15 | First commit! | Aryadev Chavali | |
This is a from the ground rework of an old project of the same name. I'm hoping to be more concerned with runtime efficiency, bytecode size and all those things that should actually matter for something that may host time/space critical code. |