diff options
author | Kartik Agaram <vc@akkartik.com> | 2019-07-15 12:26:41 -0700 |
---|---|---|
committer | Kartik Agaram <vc@akkartik.com> | 2019-07-15 12:26:41 -0700 |
commit | aef4efb959b215a2cd830e186c083c78f7bde60a (patch) | |
tree | ad3735842abc8de847ef407a83915cae4a54c26d /subx/apps/crenshaw2-1b.subx | |
parent | 867894b3efdc9c9df39d8ad9b6011f01e95e2811 (diff) | |
download | mu-aef4efb959b215a2cd830e186c083c78f7bde60a.tar.gz |
5404 - subx/examples/ex1 now translating
The result isn't an identical binary to before, and it segfaults when run. But it's bugfix seven. A couple of places where we make .subx files a little more strict: a) All .subx files must define a data segment. Even if they have no data. b) All .subx files must define an `Entry` label for the binary to start at. Earlier we used to default to the start of the code label. That's not too hard to add; we'd just need to: i) rename `get` to `get-or-abort` ii) clone a third variant of `get-or-insert` called `get` that returns null if the key is not found. iii) use `get` rather than `get-or-abort` when looking up the `Entry` label.
Diffstat (limited to 'subx/apps/crenshaw2-1b.subx')
0 files changed, 0 insertions, 0 deletions