2bf8a81dbc
96
2014-10-05 10:31:27 -07:00
bdadc933ef
95
2014-10-04 23:00:19 -07:00
133401ecbc
94 - old multiprocessing experiment
2014-10-04 20:55:03 -07:00
6e56bf32cc
93 - new project: a text-mode editor
...
New planet racket dependency: neil/charterm:3:1
2014-10-04 20:18:55 -07:00
033d558a10
92
2014-08-31 11:27:58 -07:00
339001ea83
91 - just implement ops natively to maintain momentum
2014-08-31 11:26:07 -07:00
dba1112cd9
90
2014-08-31 11:20:28 -07:00
f3b0f4dc05
89 - a simple round-robin scheduler
2014-08-28 20:44:16 -07:00
aa66c8327d
88 - a different trace testing helper
...
Verifies a set of lines in order.
2014-08-28 20:43:11 -07:00
a1ef151196
87
2014-08-28 19:54:37 -07:00
2f2c241800
86
2014-08-28 19:53:57 -07:00
0832cc89dc
85 - trace testing ahoy ( http://akkartik.name/post/tracing-tests )
2014-08-28 19:53:41 -07:00
c532f0ab5f
84
2014-08-28 19:23:38 -07:00
c140d9cc5f
83 - extract a function to run a short slice of instructions
2014-08-28 16:47:09 -07:00
fbe15a986a
82
2014-08-28 16:40:28 -07:00
d95ed21da9
81 - reify machine state into a 'context' variable
...
Beginning of concurrency primitives.
2014-08-28 14:55:10 -07:00
576d603f8f
80
2014-08-27 16:24:40 -07:00
3561e8513d
79 - purge unnecessary macros
...
Noob mistake.
2014-08-26 22:05:30 -07:00
92819aa5e3
78
2014-08-26 22:00:38 -07:00
230415b4e1
77 - 'new' in the interpreter
...
Next we'll try to reimplement it on the simulated machine. But for now,
sys.arc is extraneous.
Debugging this, the commented out prints started to become onerous enough I couldn't
bear to keep them.
2014-08-26 21:55:21 -07:00
91226d7c76
76
2014-08-26 11:52:16 -07:00
817b7e0be0
75
2014-08-26 10:17:55 -07:00
e63534dd85
74
2014-08-23 10:22:57 -07:00
ad9e48b34b
73
2014-08-23 10:17:33 -07:00
2ee76bda37
72 - broken
...
Thoroughly confused about how to manage memory at initialization time, and how
to maintain type information in the simulated machine.
2014-08-22 11:30:36 -07:00
1f18a4fd0a
71
2014-08-22 11:05:51 -07:00
2b15484f33
70
2014-08-22 10:47:44 -07:00
734e8c2824
69
2014-08-21 21:37:55 -07:00
6da81a3e4a
68
2014-08-21 21:04:45 -07:00
c7dc4ba972
67
2014-08-21 20:50:38 -07:00
0a8858dbc5
66 - bounds checking
...
Currently baked into the processor model, but eventually will be emitted
in generated code.
2014-08-21 20:40:05 -07:00
6a2edbe8ca
65 - separate op for array indexing
...
'get' no longer supports that case; that was confusing.
2014-08-21 20:35:52 -07:00
6f9bf3a063
64
2014-08-21 20:32:27 -07:00
7b6e5972d6
63
2014-08-21 20:08:22 -07:00
baf61345bf
62
2014-08-21 19:55:16 -07:00
689a480e1e
61 - 'get' for array access
...
get _ 0 => retrieves array length
get _ n => retrieves index n-1
2014-08-21 00:57:57 -07:00
0c57bf0a1b
60
2014-08-21 00:31:50 -07:00
8a93b211e4
59
2014-08-20 19:49:05 -07:00
980e1bf3ca
58
2014-08-20 17:44:20 -07:00
b9fef0471d
57 - multi-word or multi-field ops
2014-08-19 23:37:50 -07:00
f9dd51f672
56 - 'get' for record access
2014-08-19 21:33:48 -07:00
6b133a720e
55
2014-08-19 12:16:47 -07:00
624b9e86a1
54
2014-08-19 12:14:51 -07:00
889e4b958e
53 - simplest possible allocator: just one word at a time
...
But with tests this time.
2014-08-19 12:02:40 -07:00
955ecf4a45
52
2014-08-19 11:58:22 -07:00
409e66ccaf
51
2014-08-19 11:23:01 -07:00
dbe8d43671
50
2014-08-18 12:12:58 -07:00
4a0b335c28
49 - make Readme less ambiguous
...
As expected, mu works just as well with named variables.
Maybe I want to insert the local stack frame computations automatically
using the assembler? How to indicate globals then? Add 'local' metadata only
if 'global' is absent? What about lexical stack frames?
2014-08-18 10:23:24 -07:00
ab8619a148
48
2014-08-02 15:38:50 -07:00
39dd5cd491
47
2014-08-02 15:26:08 -07:00
Kartik K. Agaram