about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2017-10-16 03:30:52 -0700
committerKartik K. Agaram <vc@akkartik.com>2017-10-16 03:30:52 -0700
commit110c231ba5bff5b65ca4891de7fcd8c68d1029bf (patch)
treed1f692c026e62263d616e1c0b34578c5c0681260
parentd77745f5e95b1b52508c8e6b29672d6f4928226d (diff)
downloadmu-110c231ba5bff5b65ca4891de7fcd8c68d1029bf.tar.gz
4074
-rw-r--r--subx/Readme.md16
1 files changed, 10 insertions, 6 deletions
diff --git a/subx/Readme.md b/subx/Readme.md
index dddccb91..22a1878b 100644
--- a/subx/Readme.md
+++ b/subx/Readme.md
@@ -10,13 +10,17 @@ Bytecode interpreter for a subset of the 32-bit x86 ISA.
   unsigned numbers)
 * Only relative jump instructions (with 8-bit or 16-bit offsets).
 
-Basically a minimum basis set that a compiler for Mu can target. This isn't
-meant to run arbitrary binaries, just those generated by our compiler,
-allowing better tests for the compiler, access to processor/memory state
-without getting bogged down in details of the ELF format, ABI, STABS debugging
-format, etc., etc.
+These rules yield a clean instruction set. We don't care about running
+arbitrary binaries, just those generated by our Mu compiler.
 
-To run tests:
+Targeting a VM enables more comprehensive tests for the compiler, without
+requiring access to processor/memory state without getting bogged down in
+details of the ELF format, ABI, STABS debugging format, etc., etc.
+
+Having the VM implement a real (and ubiquitous) instruction set makes it easy
+to generate native binaries outside of tests.
+
+Just unit tests so far:
 
   ```
   ./subx test