retroforth/nga-c
crc 85502aed7a nga-c: fix hang when building
FossilOrigin-Name: acd940e821a3eedd45688297c308ae584352bbff327802dc9ee0b5f31cb26d0c
2021-04-14 11:55:46 +00:00
..
assemble.retro some experimental vm and tooling stuff (nga-c) 2021-04-08 19:51:34 +00:00
devices.retro some experimental vm and tooling stuff (nga-c) 2021-04-08 19:51:34 +00:00
extend.retro some experimental vm and tooling stuff (nga-c) 2021-04-08 19:51:34 +00:00
GNUmakefile some experimental vm and tooling stuff (nga-c) 2021-04-08 19:51:34 +00:00
image.c nga-c: fix hang when building 2021-04-14 11:55:46 +00:00
listen.retro nga-c: fix hang when building 2021-04-14 11:55:46 +00:00
Makefile nga-c: new vm: add support for embedded image 2021-04-14 11:53:01 +00:00
nga.c nga-c: new vm: add support for embedded image 2021-04-14 11:53:01 +00:00
ngaImage nga-c: fix hang when building 2021-04-14 11:55:46 +00:00
README.md some experimental vm and tooling stuff (nga-c) 2021-04-08 19:51:34 +00:00


I'm exploring some things around the VM implementation and tooling; this directory contains the relevant files for this.

Things I'm working on in this:

[x] Single file implementation [x] Modular I/O (enable/disable at compile time) [x] Faster opcode processing [x] Removal of image saving from the C sources [x] Building extended image w/o retro-extend in C [x] Assemble new image w/o retro-muri in C [ ] Support for embedding device words in the C source [ ] Embed image in the C source using tool written in Retro

Notes: this requires an external image. One is provided.

Specifics:

Retro's build process is a little messy. We first compile the assembler, then retro-extend (which is an Nga-in-C, with a reduced set of I/O). These are used to assemble the kernel, merge in the stdlib and any device words, then the VM is compiled, user-level additions are added to a new image, and then the source is updated before being rebuilt.

In this, the VM is built, then is used to assemble and build a new image, eliminating the need for separate retro-extend and retro-muri binaries.

In the longer term, there is benefit to having a standalone set of supporting tools, so I'm not going to eliminate them, but using Retro itself for more is something worth doing IMO.