about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 6611 - start adding to common vocabulary in MuKartik Agaram2020-07-052-2/+2
|
* 6610 - tweak the Linux boot image generatorKartik Agaram2020-07-051-8/+6
| | | | | So far we hardcoded the translation process and it only supported SubX. Now we pass in an ELF binary and outsource how it's generated.
* 6609Kartik Agaram2020-07-052-1/+100
|
* 6607 - new prototype dir for spreadsheet ideasKartik Agaram2020-07-051-0/+0
|
* 6606Kartik Agaram2020-07-022-59/+77
|
* 6605Kartik Agaram2020-07-013-92/+217
|
* 6604 - new appKartik Agaram2020-07-0130-1/+69
| | | | | | https://archive.org/details/akkartik-2min-2020-07-01 In the process I found a bug, added a new syscall, and 'emulated' it.
* 6603Kartik Agaram2020-06-304-41/+41
|
* 6602Kartik Agaram2020-06-3029-329/+469
|
* 6601Kartik Agaram2020-06-2934-182/+182
|
* 6600Kartik Agaram2020-06-2944-66/+66
|
* 6599Kartik Agaram2020-06-2918-28/+28
|
* 6598Kartik Agaram2020-06-291-2/+2
|
* 6597Kartik Agaram2020-06-2918-24/+24
|
* 6596Kartik Agaram2020-06-2918-48/+48
|
* 6595Kartik Agaram2020-06-2925-149/+149
|
* 6594 - start standardizing the meaning of 'print'Kartik Agaram2020-06-2918-13/+13
|
* 6593Kartik Agaram2020-06-281-17581/+18990
|
* 6592 - error-checking for integer stmts feels doneKartik Agaram2020-06-282-1/+50
|
* 6591Kartik Agaram2020-06-282-1/+32
|
* 6590Kartik Agaram2020-06-282-1/+189
|
* 6589Kartik Agaram2020-06-282-12/+5
|
* 6588Kartik Agaram2020-06-282-0/+165
|
* 6587Kartik Agaram2020-06-282-0/+166
|
* 6586 - error-checking for 'get' stmts feels doneKartik Agaram2020-06-282-1/+111
|
* 6585Kartik Agaram2020-06-282-10/+97
|
* 6584Kartik Agaram2020-06-282-0/+55
|
* 6583Kartik Agaram2020-06-282-1/+61
|
* 6582Kartik Agaram2020-06-282-2/+69
|
* 6581Kartik Agaram2020-06-282-6/+259
|
* 6580Kartik Agaram2020-06-281-4/+4
|
* 6579Kartik Agaram2020-06-282-5/+143
|
* 6578 - redo error if 'get' on unknown fieldKartik Agaram2020-06-272-78/+117
| | | | | | This commit reimplements commit 6515 to happen during type-checking rather than as early as possible. That way we naturally get a more informative error message.
* 6577Kartik Agaram2020-06-272-12/+12
|
* 6576Kartik Agaram2020-06-272-8/+56
|
* 6575Kartik Agaram2020-06-272-220/+253
|
* 6574Kartik Agaram2020-06-271-4/+6
|
* 6573Kartik Agaram2020-06-212-16/+16
|
* 6572Kartik Agaram2020-06-214-10193/+10253
| | | | | Small change to mu.subx to keep the treeshaker working with it. That's currently the only place where we prevent jumps across 'functions'.
* 6571Kartik Agaram2020-06-212-17370/+18159
|
* 6570 - error on use of a clobbered varKartik Agaram2020-06-218-68/+195
| | | | | All tests now passing, and factorial.mu and all other apps now working. The new checks caught one problem in a few prototypes.
* 6569 - correct the second failing testKartik Agaram2020-06-211-34/+31
|
* 6568Kartik Agaram2020-06-211-3/+3
|
* 6567Kartik Agaram2020-06-211-14/+11
|
* 6566 - improve some error messagesKartik Agaram2020-06-211-111/+165
| | | | | I need to pass the function around to fix the failing test; might as well fix the error messages while I'm at it.
* 6565 - support tmux in control modeKartik Agaram2020-06-211-2/+2
| | | | | https://github.com/tmux/tmux/wiki/Control-Mode https://www.iterm2.com/documentation-tmux-integration.html
* 6564 - second failing testKartik Agaram2020-06-211-0/+61
|
* 6563Kartik Agaram2020-06-211-19/+19
| | | | | | | | | | The desire captured by a test is often hard to verbalize, path-dependent and more fertile for the future than its original impulse. On some level, someone wanting to rip out features has to just ask for each scenario, "what do I want to happen here?" And nobody's gonna do that. At best, somebody may be trying to rip out some complex feature, and run into some collateral damage around the edges that they have to inspect more closely. "Do I care about preserving this behavior?"
* 6562Kartik Agaram2020-06-212-19/+46
| | | | | | | | | | | | | | | | | | | | | | | | The new failing test is now passing, and so is this manual test that had been throwing a spurious error: fn foo { var a/eax: int <- copy 0 var b/ebx: int <- copy 0 { var a1/eax: int <- copy 0 var b1/ebx: int <- copy a1 } b <- copy a } However, factorial.mu is still throwing a spurious error. Some history on this commit's fix: When I moved stack-location tracking out of the parsing phase (commit 6116, Mar 10) I thoughtlessly moved block-depth tracking as well. And the reason that happened: I'd somehow gotten by without ever cleaning up vars from a block during parsing. For all my tests, this is a troubling sign that I'm not testing enough. The good news: clean-up-blocks works perfectly during parsing.
* 6561 - failing testKartik Agaram2020-06-211-8/+122
| | | | | Test `test-shadow-name-2` shows that we aren't popping off more than one variable from each block that we exit.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-14 13:36:42 +0000