Stop requiring '--debug' in 'bootstrap run'. Now it's smart enough to turn
on when needed.
This creates some small chance of reading stale debug info for the wrong
binary, but in practice that hasn't been an issue.
Just clarified for myself why `subx translate` and `subx run` need to share
code: emulation supports the tests first and foremost.
In the process we clean up our architecture for levels of layers. It's
a good idea but unused once we reconceive of "level 1" as just part of
the test harness.
Rename a few scripts to be more consistent.
I'm also starting to feel the urge to bud off `subx run` into its own program,
say tools/emulate_x86. It doesn't really rely on the SubX notation at all.
And then I could rename `subx translate` to `translate_subx_bootstrap`.
Only problem: the commands in the Readme get verbose. But the Readme is
gonna need surgery soon anyway to put translate_mu front and center.
I can now run this program:
fn main -> result/ebx: int {
result <- do-add 3 4
}
fn do-add a: int, b: int -> result/ebx: int {
result <- copy a
result <- add b
}
We still can't define local variables, but can write any programs involving
ints by passing in enough arguments for temporaries.
Extremely crappy syntax highlighting for Emacs. I just can't wrap my head
around elisp, and I'm inclined to blame elisp. Checking this off my todo
list and moving on.
We haven't implemented it yet, but there's now a design for how we check
whether a function has written its output correctly. Functions must write
to each output at the top level at least once, and never overwrite an output
register in the top-level once it's been defined.
This is conservative (it can be perfectly reasonable for functions to write
the output, reuse the register for a temporary, and then write the output
again) but easy to check.
Kartik Agaram