akkartik
/
mu
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
mu/linux/ex1.subx

19 lines
381 B
Plaintext
Raw Normal View History

4808 - clean up comments in all subx files
2018-12-01 00:45:15 +00:00
# First program: same as https://www.muppetlabs.com/~breadbox/software/tiny/teensy.html
4351
2018-07-16 14:55:07 +00:00
# Just return 42.
4303 - subx: first real transform We'll see if this is useful. Mostly just stretching our legs.
2018-07-01 07:01:13 +00:00
#
5521
2019-08-20 06:45:04 +00:00
# To run:
-
2020-05-08 06:12:29 +00:00
# $ ./bootstrap translate init.linux apps/ex1.subx -o apps/ex1
6089
2020-03-07 02:07:39 +00:00
# $ ./bootstrap run apps/ex1
4446
2018-07-27 23:53:47 +00:00
# Expected result:
# $ echo $?
# 42
4303 - subx: first real transform We'll see if this is useful. Mostly just stretching our legs.
2018-07-01 07:01:13 +00:00
5647 - experimental support for swapping OS
2019-09-12 02:04:49 +00:00
== code
4780
2018-11-26 08:26:20 +00:00
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.
2019-07-15 19:26:41 +00:00
Entry:
5647 - experimental support for swapping OS
2019-09-12 02:04:49 +00:00
# exit(42)
5872
2020-01-02 22:12:46 +00:00
bb/copy-to-ebx 0x2a/imm32 # 42 in hex
5647 - experimental support for swapping OS
2019-09-12 02:04:49 +00:00
e8/call syscall_exit/disp32
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.
2019-07-15 19:26:41 +00:00
4802 Some automated commenting cleanup. Still needs more careful manual scanning. sed -i 's/^# 1-3/# . 1-3/' *.subx */*.subx sed -i 's/^# op/# . op/' *.subx */*.subx sed -i 's/# vim/# . . vim/' *.subx */*.subx sed -i 's/^ # push args/ # . . push args/' *.subx */*.subx sed -i 's/^ # discard args/ # . . discard args/' *.subx */*.subx sed -i 's/^ # call/ # . . call/' *.subx */*.subx sed -i 's/^ # prolog/ # . prolog/' *.subx */*.subx sed -i 's/^ # epilog/ # . epilog/' *.subx */*.subx sed -i 's/^ # save registers/ # . save registers/' *.subx */*.subx sed -i 's/^ # restore registers/ # . restore registers/' *.subx */*.subx sed -i 's/ operand / register /' *.subx */*.subx
2018-11-30 19:10:44 +00:00
# . . vim:nowrap:textwidth=0