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 0975d92493 Introduced new instructions for comparison

Comparing signed and unsigned versions of numbers.  Same for EQ as
well.

Notice the irregular pattern of BYTE, CHAR, INT, HWORD,LONG,WORD as
OPCODE_IS_TYPE requires the subcodes to be surrounded by BYTE and
WORD.

2023-10-31 20:50:28 +00:00

.github/workflows

Remove unit tests from github workflow

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

asm

asm/main logs are now indented and look prettier

2023-10-31 20:39:49 +00:00

examples

Changed asm/parser instruction push-reg->push.reg

2023-10-31 20:37:11 +00:00

lib

Added a "usage" message and colours for assembler

2023-10-29 16:59:31 +00:00

Introduced new instructions for comparison

2023-10-31 20:50:28 +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

Make Verbose a universal flag

2023-10-29 16:59:37 +00: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.