Archived

This repository has been archived on 2025-11-10. You can view files and clone it. You cannot open issues or pull requests or push a commit.

Go to file

Aryadev Chavali c4cb45f3ad Fixed bug where reading operand bytecode may stop prematurely

This is due to checking for equality instead of just greater than in
darr->used against darr->available.

2023-10-29 16:56:33 +00:00

.github/workflows

Remove unit tests from github workflow

2023-10-15 01:27:46 +01:00

asm

Introduce error reporting in asm/main

2023-10-28 18:22:18 +01:00

examples

Added some examples to instruction-test for positive/negative literals

2023-10-29 16:56:19 +00:00

lib

Auto-fill copyright notice in examples/fib.c

2023-10-29 16:56:19 +00:00

Fixed bug where reading operand bytecode may stop prematurely

2023-10-29 16:56:33 +00:00

.dir-locals.el

Make root directory an include path, set #include's properly

2023-10-23 04:46:09 +01:00

.gitignore

First commit!

2023-10-15 01:25:24 +01:00

LICENSE

First commit!

2023-10-15 01:25:24 +01:00

Makefile

Implemented a rudimentary parser with support for 4 instruction types

2023-10-26 11:17:55 +01:00

README.org

Updated README for targeting VM

2023-10-26 10:22:26 +01:00

README.org

Oreo's Virtual Machine (OVM)

Instructions to target

A stack based virtual machine in C11. Deals primarily in bytes, doesn't make assertions about typing and is very simple to target.

Instructions to target

You need to link with the object files for base.c, darr.c and inst.c to be able to properly target the OVM. The basic idea is to create instructions via inst_t then using the inst(s)_write_* API to generate bytecode (and write to a file).

Then to execute the program, the virtual machine interpreter ovm.out is used.