about summary refs log tree commit diff stats
path: root/apps/mu.subx
Commit message (Collapse)AuthorAgeFilesLines
* 5831Kartik Agaram2019-12-271-27/+38
|
* 5830Kartik Agaram2019-12-261-1/+5
| | | | | Bugfix: statements defining a new register variable require an initializer instruction.
* 5828 - copy (mov) instructionsKartik Agaram2019-12-261-22/+144
|
* 5827 - give primitives one more bit of metadataKartik Agaram2019-12-261-4/+59
| | | | | Copy (mov) instructions are unlike instructions we've encoded so far, in that their destination is not read.
* 5826 - done with basic binary opsKartik Agaram2019-12-261-0/+197
|
* 5825 - code-generation for add opcodesKartik Agaram2019-12-261-26/+158
|
* 5824 - code-generation for all inc/dec opcodesKartik Agaram2019-12-261-2/+199
|
* 5823Kartik Agaram2019-12-221-0/+55
|
* 5821 - now translating function argumentsKartik Agaram2019-12-221-110/+156
| | | | See test-convert-function-with-arg-and-body.
* 5820Kartik Agaram2019-12-221-38/+177
| | | | | | | | | | | One test failing. It took enough debugging just to get to the expected failure that it seems worth saving this snapshot. Saw some signs that I have to remember to zero-out allocated memory. We need a scalable solution for this. I think parse-var-with-type needs to be rewritten. Just added a test and a hacky fix for now.
* 5804Kartik Agaram2019-12-081-222/+229
| | | | | Try to make the comments consistent with the type system we'll eventually have.
* 5795Kartik Agaram2019-12-071-1/+5
|
* 5790Kartik Agaram2019-12-051-23/+23
| | | | | | Standardize conventions for labels within objects in the data segment. We're going to use this in a new tool.
* 5785 - initial skeleton for parsing fn bodiesKartik Agaram2019-11-301-5/+21
| | | | | All tests passing again. We have big gaping holes for type- and var-management. We're going to work on the latter first.
* 5784Kartik Agaram2019-11-301-7/+27
| | | | | Lots of debugging to add two curly braces. I need tests for populate-mu-function-body, or even parse-mu-block.
* 5782 - fix a widespread bug with Heap-sizeKartik Agaram2019-11-301-1/+1
|
* 5781Kartik Agaram2019-11-301-3/+194
| | | | | parse-mu-stmt now working, though we'll need to go back and stop creating a new var for every instance of a variable in a scope.
* 5780Kartik Agaram2019-11-291-43/+50
|
* 5779Kartik Agaram2019-11-291-100/+308
| | | | | Snapshot with new skeleton for parsing function body. New test still failing, but only in the one expected place.
* 5778Kartik Agaram2019-11-291-19/+19
|
* 5777Kartik Agaram2019-11-291-3/+159
|
* 5776Kartik Agaram2019-11-291-34/+48
|
* 5775Kartik Agaram2019-11-291-9/+105
|
* 5774Kartik Agaram2019-11-291-26/+82
| | | | Function headers seem to be parsing right.
* 5773Kartik Agaram2019-11-281-0/+205
| | | | Rudimentary support for parsing variable declarations.
* 5772Kartik Agaram2019-11-281-0/+110
|
* 5770Kartik Agaram2019-11-281-0/+189
|
* 5768 - start parsing fn headersKartik Agaram2019-11-271-14/+63
|
* 5767Kartik Agaram2019-11-271-16/+175
| | | | Some groundwork for parsing.
* 5765Kartik Agaram2019-11-261-0/+112
| | | | | | | | | A couple more primitives now working. In the process I ran into an issue with some buffer filling up when running ntranslate. Isolating it to survey.subx was straightforward, but --trace ran out of RAM, and --trace --dump ran out of (7GB of) disk. In the end what helped was just repeatedly inserting exits at different points, and I realized there was a magic number that hadn't been turned into a named constant.
* 5763Kartik Agaram2019-11-261-12/+64
|
* 5762Kartik Agaram2019-11-261-5/+0
|
* 5761Kartik Agaram2019-11-261-2/+43
|
* 5760Kartik Agaram2019-11-251-8/+31
|
* 5759 - design statement data structureKartik Agaram2019-11-251-14/+80
|
* 5756Kartik Agaram2019-11-181-12/+30
|
* 5755Kartik Agaram2019-11-181-0/+66
| | | | Support function calls with literal arguments.
* 5754Kartik Agaram2019-11-181-3/+81
| | | | Support binary instructions with an immediate operand.
* 5752Kartik Agaram2019-11-181-77/+97
| | | | | | | Support binary operations with reg/mem and reg operands. Everything is passing. However, the self-hosting translator now generates some discrepancies compared to the C++ translator :(
* 5751 - start of table of Mu primitivesKartik Agaram2019-11-181-0/+168
| | | | | So far this is just the same as our most recent tests. But now we have a 'DSL' for adding more primitives.
* 5750Kartik Agaram2019-11-171-25/+411
| | | | | We can now compile primitive statements while selecting the right template to code-gen each one from. Even when multiple templates have the same name.
* 5746Kartik Agaram2019-11-151-37/+336
| | | | | | | | | | | | | | | | After much struggle, one more test: emitting a primitive with a register operand. The following two instructions have the same name: reg <- increment increment var and they emit the same opcodes: ff 0/subop But they're considered distinct policies in the code-generation 'table', one for incrementing variables on the stack and the other for incrementing variables in a register.
* 5745Kartik Agaram2019-11-141-35/+71
| | | | | | I've been under-estimating the complexity of translating primitive statements. We need to separately track information for each primitive about operands for both the source and emitted SubX notation.
* 5744Kartik Agaram2019-11-141-9/+5
|
* 5743Kartik Agaram2019-11-141-1/+1
|
* 5742Kartik Agaram2019-11-141-7/+5
| | | | No, let's represent register as just a string to save a translation.
* 5741Kartik Agaram2019-11-141-9/+19
| | | | | Support variables at positive stack offsets (formal parameters for functions), and also an indicator for 'any register' for primitive operations.
* 5740Kartik Agaram2019-11-141-4/+0
|
* 5737 - first 2 Mu statements translating to SubXKartik Agaram2019-11-101-15/+64
|
* 5736Kartik Agaram2019-11-101-47/+69
| | | | | | | | Rethink how vars are organized. We need separate aggregates for vars in the definition stack, defined in function headers, and used by statement operands. So now vars have no 'next' fields themselves. The definition stack will be a real stack, while the function headers and statement operands will have separate 'next' fields.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-02 15:14:27 +0000