diff options
| author | Aryadev Chavali <aryadev@aryadevchavali.com> | 2023-10-31 21:15:39 +0000 |
|---|---|---|
| committer | Aryadev Chavali <aryadev@aryadevchavali.com> | 2023-10-31 21:15:39 +0000 |
| commit | 92ccdfe95c7143871843ac0ddaa6e7b0e0f7061d (patch) | |
| tree | 8187c842b6378b011781df3f5eed7ace6b7d62f7 | |
| parent | 5d800d43668360b5752277108247fdd5c5069301 (diff) | |
| download | ovm-92ccdfe95c7143871843ac0ddaa6e7b0e0f7061d.tar.gz ovm-92ccdfe95c7143871843ac0ddaa6e7b0e0f7061d.tar.bz2 ovm-92ccdfe95c7143871843ac0ddaa6e7b0e0f7061d.zip | |
Fixed README for change in inst module
| -rw-r--r-- | README.org | 7 |
1 files changed, 5 insertions, 2 deletions
@@ -7,9 +7,12 @@ doesn't make assertions about typing and is very simple to target. * Instructions to target You need to link with the object files for [[file:lib/base.c][base.c]], [[file:lib/darr.c][darr.c]] and -[[file:vm/inst.c][inst.c]] to be able to properly target the OVM. The -basic idea is to create instructions via ~inst_t~ then using the +[[file:lib/inst.c][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. + +For clarity, one may build ~lib~ (~make lib~) then use the resulting +object files to link and create bytecode for the virtual machine. |