about summary refs log tree commit diff stats
path: root/apps
Commit message (Collapse)AuthorAgeFilesLines
* 6382 - re-enable mu.subx in CIKartik Agaram2020-05-2211-21/+21
| | | | | | | | | | | I thought I'd done this in the previous commit, but I hadn't. And, what's more, there was a bug that seemed pretty tough for a time. Turns out my self-hosted translator doesn't support '.' comment tokens in data segments. Hopefully I'm past the valley of the shadow of death now. "I HAVE NO TOOLS BECAUSE I’VE DESTROYED MY TOOLS WITH MY TOOLS." -- James Mickens (https://www.usenix.org/system/files/1311_05-08_mickens.pdf)
* update binariesKartik Agaram2020-05-2213-0/+0
| | | | CI should start passing again now.
* increase some buffer sizesKartik Agaram2020-05-221-2/+2
| | | | We can now natively translate mu.subx again.
* mu.subx is now using handles everywhereKartik Agaram2020-05-221-5/+8
| | | | X-( :-))
* mu.subx: 4 failing tests remainingKartik Agaram2020-05-221-11/+37
|
* mu.subx: 6 failing tests remainingKartik Agaram2020-05-221-97/+313
|
* mu.subx: 7 failing tests remainingKartik Agaram2020-05-211-10/+14
| | | | Just for user-defined types.
* mu.subx: 9 failing tests remainingKartik Agaram2020-05-211-29/+40
|
* mu.subx: 11 failing tests remainingKartik Agaram2020-05-211-30/+40
|
* mu.subx: 13 failing tests remainingKartik Agaram2020-05-211-11/+13
|
* mu.subx: 2 new testsKartik Agaram2020-05-201-0/+97
|
* mu.subx: 15 failing tests remainingKartik Agaram2020-05-201-9/+10
| | | | The remaining tests are all for user-defined types and arrays.
* mu.subx: 17 failing tests remainingKartik Agaram2020-05-201-17/+18
|
* -Kartik Agaram2020-05-201-6/+4
|
* mu.subx: 21 failing tests remainingKartik Agaram2020-05-201-5/+5
|
* mu.subx: 24 failing tests remainingKartik Agaram2020-05-201-49/+54
|
* mu.subx: 25 failing tests remainingKartik Agaram2020-05-201-6/+21
| | | | | | | | | | | | | | | | | This was again hard to debug, because: - the mapping between recursive calls to emit-subx-stmt-list and the nested blocks of code in the output kept blowing my stack, and - I kept expecting the problem to be there, or in the data attached to variables. But it was in the `emit-cleanup-code-until-depth` for the previous/inner block, in code I thought I'd already fixed (`clean-up-blocks`) that accidentally worked for previous tests. Part of the problem here is that my library for the stack sucks. It's only for 4-byte elements, but I'm using it for 8-byte elements (handles). Which leads to double-pushes and double-pops and -- here -- an insidiously wrong call to `top`. Anyways: halfway there!
* mu.subx: 26 failing tests remainingKartik Agaram2020-05-201-9/+11
|
* mu.subx: 28 failing tests remainingKartik Agaram2020-05-201-10/+35
| | | | | This bug was a bear to track down, but there's been a concomitant payoff: 6 tests starting to pass.
* mu.subx: 34 failing tests remainingKartik Agaram2020-05-201-36/+49
|
* -Kartik Agaram2020-05-201-4/+4
|
* mu.subx: 37 failing tests remainingKartik Agaram2020-05-201-11/+13
|
* mu.subx: 39 failing tests remainingKartik Agaram2020-05-201-31/+31
|
* mu.subx: start tracking remaining failing testsKartik Agaram2020-05-201-40/+40
| | | | We're now passing CI again.
* mu.subx: 10/50 top-level tests passingKartik Agaram2020-05-181-2/+3
|
* mu.subx: 6/50 top-level tests passingKartik Agaram2020-05-181-8/+16
|
* mu.subx: 4/50 top-level tests passingKartik Agaram2020-05-181-1/+2
|
* mu.subx: 3/50 top-level tests passingKartik Agaram2020-05-181-1/+1
|
* mu.subx: 2/50 top-level tests passingKartik Agaram2020-05-181-31/+33
|
* mu.subx: done with code-generation testsKartik Agaram2020-05-181-18/+44
| | | | Bottom 42 of 92 tests are now passing. Time for the first 50.
* mu.subx: test-emit-subx-stmt-function-callKartik Agaram2020-05-181-30/+73
|
* mu.subx: test-compare-reg-with-literalKartik Agaram2020-05-181-21/+68
|
* mu.subx: test-compare-eax-with-literalKartik Agaram2020-05-181-22/+70
|
* mu.subx: compare-mem-with-literalKartik Agaram2020-05-181-21/+64
|
* mu.subx: test-compare-reg-with-memKartik Agaram2020-05-181-19/+61
|
* mu.subx: test-compare-mem-with-regKartik Agaram2020-05-181-22/+65
|
* mu.subx: test-add-literal-to-memKartik Agaram2020-05-181-20/+63
|
* mu.subx: test-add-literal-to-regKartik Agaram2020-05-181-32/+82
|
* mu.subx: test-add-literal-to-eaxKartik Agaram2020-05-181-23/+72
|
* mu.subx: test-add-mem-to-regKartik Agaram2020-05-181-18/+61
|
* -Kartik Agaram2020-05-181-34/+34
|
* -Kartik Agaram2020-05-181-254/+272
|
* mu.subx: test-add-reg-to-memKartik Agaram2020-05-181-20/+64
|
* mu.subx: test-add-reg-to-reg passingKartik Agaram2020-05-181-12/+15
|
* mu.subx: add handles to remaining declsKartik Agaram2020-05-181-20/+102
| | | | test-add-reg-to-reg should pass now. But it doesn't..
* mu.subx: next test now successfully scans primitivesKartik Agaram2020-05-181-16/+63
| | | | Still failing.
* mu.subx: switch SubX instruction names to globalsKartik Agaram2020-05-181-81/+81
| | | | | | Entirely using interactive search-and-replace in my text editor. This is all ugly as hell. But get it working first.
* mu.subx: switch Mu instruction names to globalsKartik Agaram2020-05-181-80/+80
|
* mu.subx: global decls for all string handlesKartik Agaram2020-05-181-116/+645
| | | | | | | | | | My previous approach was way too slow. Now I just `grep`d for all string literals in the `Primitives` block, and piped them through: while read X; do echo $X |tools/expand_string_handle; done Still required some post-processing, but orders of magnitude faster and more amenable to batch-processing.
* -Kartik Agaram2020-05-181-17/+124
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-23 07:59:50 +0000