about summary refs log tree commit diff stats
path: root/apps
Commit message (Collapse)AuthorAgeFilesLines
* starting to fix mu.subxKartik Agaram2020-05-181-37/+42
| | | | | Update offset declarations in function data structures for starters. We still need to go over the entire file to actually use them.
* -Kartik Agaram2020-05-181-6/+6
|
* all syntax sugar now workingKartik Agaram2020-05-184-12/+36
| | | | | | | | I just needed to adjust row-sizes when accessing the Registers table. This commit dedicated to a fun hour on https://hn.town.siempre.io. Thanks Cyrus! (via https://news.ycombinator.com/item?id=22818300)
* support 'fake' handles allocated staticallyKartik Agaram2020-05-189-0/+0
| | | | | | | | Mystery solved of why the syntax sugar phases don't work even though they don't use any functions whose signatures changed in the migration to handles. The answer: they use the Registers table, and it needs to use handles rather than raw strings.
* support 'fake' handles allocated staticallyKartik Agaram2020-05-189-0/+0
| | | | | | | | | | | | | | | | | | | | | | Mystery solved of why the syntax sugar phases don't work even though they don't use any functions whose signatures changed in the migration to handles. The answer: they use the Registers table, and it currently doesn't use handles. Rather than create a whole new set of functions that operate on addresses, I'm going to create fake handles that are never intended to be reclaimed. Which raises the question of the best way to do that. I'd like to continue using string syntax, so I'm going to use a prefix in the payload that can also be rendered as a string. But all the printable characters start with 0x20, and we don't currently have escape sequences for null or any other non-printable characters. I _could_ use newlines, but that seems overly clever. So instead I'll once again not worry about some hypothetical problem with running out of alloc-ids, and just carve out half of the id space that can't be used for real alloc ids. Ascii doesn't use the most significant bit of bytes, so it seems like a natural separation.
* fix a discrepancy in the generated apps/ex1 binaryKartik Agaram2020-05-182-1/+1
|
* fix a crash when translating apps/ex1Kartik Agaram2020-05-182-6/+6
|
* Rebuild phases of self-hosted SubX translatorKartik Agaram2020-05-189-0/+0
| | | | For this one commit we need to bootstrap ourselves with subx_translate_debug.
* survey.subx now workingKartik Agaram2020-05-181-265/+51
|
* emit-segments in survey.subx now workingKartik Agaram2020-05-181-72/+104
|
* second test also passingKartik Agaram2020-05-181-14/+79
|
* compute-addresses now working? Maybe?Kartik Agaram2020-05-181-92/+375
|
* compute-offsets in survey.subx now workingKartik Agaram2020-05-181-59/+100
|
* -Kartik Agaram2020-05-181-4/+13
|
* -Kartik Agaram2020-05-181-4/+4
|
* -Kartik Agaram2020-05-181-21/+23
|
* -Kartik Agaram2020-05-181-45/+0
|
* -Kartik Agaram2020-05-181-1/+1
|
* -Kartik Agaram2020-05-181-74/+0
|
* assort.subx now workingKartik Agaram2020-05-181-41/+196
|
* dquotes.subx now workingKartik Agaram2020-05-181-6/+21
|
* tests.subx now workingKartik Agaram2020-05-181-6/+23
|
* table primitives workingKartik Agaram2020-05-183-428/+1
| | | | $ ./translate_subx init.linux 0*.subx && ./a.elf test
* 6219Kartik Agaram2020-05-182-0/+3
|
* 6216Kartik Agaram2020-05-052-12/+7
|
* 6213Kartik Agaram2020-04-262-2/+32
| | | | Some minor tweaks while preparing presentation to Mek's Junto group.
* 6212Kartik Agaram2020-04-251-1/+1
|
* 6209Kartik Agaram2020-04-241-1/+2
|
* 6208Kartik Agaram2020-04-2215-16/+2
|
* 6205Kartik Agaram2020-04-152-156/+31
| | | | Rip out scaffolding for function overloading.
* 6204Kartik Agaram2020-04-152-28/+0
|
* 6203Kartik Agaram2020-04-122-115/+162
|
* 6199Kartik Agaram2020-04-081-1/+1
|
* 6198Kartik Agaram2020-04-082-14/+10
|
* 6197Kartik Agaram2020-04-082-18/+18
|
* 6196Kartik Agaram2020-04-062-2/+2
|
* 6195Kartik Agaram2020-04-062-1/+1
| | | | This bug was never caught because we've never tested with more than 2 segments.
* 6194Kartik Agaram2020-04-062-3/+6
|
* 6193Kartik Agaram2020-04-062-3/+6
|
* 6192Kartik Agaram2020-04-062-3/+6
|
* 6191Kartik Agaram2020-04-062-5/+6
|
* 6190Kartik Agaram2020-04-061-31/+33
|
* 6189Kartik Agaram2020-04-062-15/+14
|
* 6188Kartik Agaram2020-04-061-7/+18
|
* 6187Kartik Agaram2020-04-062-1/+3
|
* 6186Kartik Agaram2020-04-062-6/+2
|
* 6185Kartik Agaram2020-04-061-8/+8
|
* 6184Kartik Agaram2020-04-051-0/+0
| | | | Why the heck are we bumping this pointer? Seems like a bug.
* 6182 - start of support for safe handlesKartik Agaram2020-04-0319-59/+59
| | | | | | | | | | | | | | So far it's unclear how to do this in a series of small commits. Still nibbling around the edges. In this commit we standardize some terminology: The length of an array or stream is denominated in the high-level elements. The _size_ is denominated in bytes. The thing we encode into the type is always the size, not the length. There's still an open question of what to do about the Mu `length` operator. I'd like to modify it to provide the length. Currently it provides the size. If I can't fix that I'll rename it.
* 6181Kartik Agaram2020-04-0317-8/+10
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-07 13:30:41 +0000