about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorKartik Agaram <vc@akkartik.com>2019-07-26 12:16:02 -0700
committerKartik Agaram <vc@akkartik.com>2019-07-26 12:16:02 -0700
commit16fa6d17a9d96e0f31c7837f510914e2c2be6bab (patch)
tree20a5190009c555bae120e766687cb159c027a4b8
parente355c6931091decf8956878e205fff74afb945a2 (diff)
downloadmu-16fa6d17a9d96e0f31c7837f510914e2c2be6bab.tar.gz
5483
-rw-r--r--subx/Readme.md20
1 files changed, 14 insertions, 6 deletions
diff --git a/subx/Readme.md b/subx/Readme.md
index fdd1aab0..b6f3e291 100644
--- a/subx/Readme.md
+++ b/subx/Readme.md
@@ -77,15 +77,23 @@ You can use SubX to translate itself. For example, running natively on Linux:
   $ ./a.elf
   $ echo $?
   42
+
+  # or, automating the above steps
+  $ ./ntranslate ex1.subx
+  $ chmod +x a.elf
+  $ ./a.elf
+  $ echo $?
+  42
   ```
 
-This is just a demonstration; in practice you would use the `ntranslate`
-script. For running emulated on other platforms, use the `translate` script.
-You'll need 16GB RAM for translating some of the larger programs in emulated
-mode. Requirements for native translation are, of course, minimal.
+Or, running in a VM on other platforms:
 
-To my knowledge the original C++ and new self-hosted translators always
-generate identical binaries. Please [report bugs](mailto:mu@akkartik.com)!
+  ```
+  $ ./translate ex1.subx  # generates identical a.elf to above
+  $ ./subx run a.elf
+  $ echo $?
+  42
+  ```
 
 You can use it to learn about the x86 processor that (almost certainly) runs
 your computer. (See below.)