about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 6405Kartik Agaram2020-05-252-2/+2
|
* 6404Kartik Agaram2020-05-251-10/+39
|
* 6403Kartik Agaram2020-05-242-1/+1
|
* 6402Kartik Agaram2020-05-241-1/+1
|
* 6401 - have scripts follow the Unix wayKartik Agaram2020-05-242-20/+0
| | | | | | | Stay silent if all is well. I don't agree with this, but it's not like the messages I was printing out were particularly useful.
* 6400Kartik Agaram2020-05-242-1/+9
|
* 6399 - make mu.vim work better out of the boxKartik Agaram2020-05-241-2/+6
| | | | | | Adding some more colors will improve the experience, but the choices depend on colorscheme, and first impressions should at least not seem to have degraded things.
* 6398Kartik Agaram2020-05-242-4/+4
|
* 6397Kartik Agaram2020-05-2428-1336/+1336
| | | | | Drop '---' section boundaries from filenames. I noticed them confusing tab-completion for certain advanced shell setups.
* 6396Kartik Agaram2020-05-245-14130/+14707
|
* 6395Kartik Agaram2020-05-241-0/+2
|
* 6394 - a catastrophic bugKartik Agaram2020-05-243-1/+14
| | | | | | | How did new-literal ever work?! Somehow we had eax silently being clobbered without affecting behavior over like 5 apps. Unsafe languages suck. Anyways, factorial.mu is now part of CI.
* 6393 - start running .mu apps in CIKartik Agaram2020-05-245-12/+73
|
* 6392 - 'length' instruction done in all complexityKartik Agaram2020-05-244-5/+322
|
* 6391Kartik Agaram2020-05-242-45/+86
|
* 6390 - return `length` in elementsKartik Agaram2020-05-243-23/+113
|
* 6389Kartik Agaram2020-05-241-9/+14
|
* 6388 - fix regression #1Kartik Agaram2020-05-242-19/+118
|
* 6387Kartik Agaram2020-05-232-19/+69
|
* 6386 - documentation on editor setupKartik Agaram2020-05-231-0/+16
|
* 6385Kartik Agaram2020-05-231-4/+4
|
* 6384Kartik Agaram2020-05-2244-14625/+19169
|
* 6383Kartik Agaram2020-05-221-3/+5
|
* 6382 - re-enable mu.subx in CIKartik Agaram2020-05-2212-25/+25
| | | | | | | | | | | 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-222-3/+3
| | | | We can now natively translate mu.subx again.
* handles don't seem to have slowed down test_appsKartik Agaram2020-05-221-4/+4
| | | | | | At least the non-native first phase which takes longer. But maybe a shorter baseline is the right thing to check. I need to resize some buffers to get Mu natively translating 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-223-99/+316
|
* 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-202-6/+6
|
* mu.subx: 24 failing tests remainingKartik Agaram2020-05-201-49/+54
|
* mu.subx: 25 failing tests remainingKartik Agaram2020-05-202-6/+24
| | | | | | | | | | | | | | | | | 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-202-52/+52
| | | | 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
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-04 22:13:21 +0000