From 64bf0e8b972e9d89b7dd8aeceac418f9e372dcc6 Mon Sep 17 00:00:00 2001 From: Kartik Agaram Date: Sun, 7 Jun 2020 15:43:13 -0700 Subject: 6499 --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 8243d29d..aad6253d 100644 --- a/README.md +++ b/README.md @@ -21,7 +21,7 @@ Running the code you want to run, and nothing else. Mu requires just a Unix-like OS and nothing else. The Mu translator is built up from machine code. You can also bootstrap it from C++. Both C++ and self-hosted versions emit identical binaries. The generated binaries require -just a Unix-like kernel and nothing else. (There are more details in [this paper](http://akkartik.name/akkartik-convivial-20200315.pdf).) +just a Unix-like kernel and nothing else. (There are more details in [this paper](http://akkartik.name/akkartik-convivial-20200607.pdf).) ## Goals @@ -69,7 +69,7 @@ variables. Most statements in Mu translate to [a single machine-code instruction Variables reside in memory by default. Programs must specify registers when they want to use them. Functions must return results in registers. Execution begins at the function `main`, which always returns its result in register -`ebx`. [The paper](http://akkartik.name/akkartik-convivial-20200315.pdf) has +`ebx`. [The paper](http://akkartik.name/akkartik-convivial-20200607.pdf) has more details, and there's a [summary](mu_summary) of all supported instructions. ## SubX -- cgit 1.4.1-2-gfad0 mmit/test/all_tests.py?h=v1.9.1&id=d0d194d886561622f4b5784ec0b23b8450fa8c2f'>commit diff stats
path: root/test/all_tests.py
blob: 0c184df5d20154871240c96b291c3ecfb595e3c8 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37