about summary refs log tree commit diff stats
path: root/apps
Commit message (Collapse)AuthorAgeFilesLines
* 7197 - tile: render screen contents and cursorKartik Agaram2020-11-061-10/+38
|
* 7196 - tile: render empty screenKartik Agaram2020-11-062-19/+80
|
* 7195 - tile: create 'screen' objectsKartik Agaram2020-11-064-0/+61
|
* 7194Kartik Agaram2020-11-062-45/+51
|
* 7193 - tile: extract taxonomy of values into a separate fileKartik Agaram2020-11-063-206/+208
|
* 7192 - more checks around literalsKartik Agaram2020-11-052-22/+318
| | | | | | | We can copy non-zero literals only to non-addr non-offset scalars. This change is surprisingly short for the magnitude of the limb I felt myself going out on for it. Surprising that there were no unpleasant discoveries.
* 7191Kartik Agaram2020-11-052-35/+55
|
* 7190Kartik Agaram2020-11-052-5/+5
| | | | Training sights now on some gaps with offset types.
* 7189 - some validations on function nameKartik Agaram2020-11-052-0/+273
| | | | Mu has no overloading or static dispatch for now.
* 7188 - raise error on deref of var on stackKartik Agaram2020-11-052-1/+74
|
* 7185 - type checks for 'populate-stream'Kartik Agaram2020-11-052-4/+437
| | | | Lots of copy-pasta.
* 7184 - type checks for 'populate'Kartik Agaram2020-11-052-7/+447
|
* 7183 - type checks for 'allocate'Kartik Agaram2020-11-052-1/+347
|
* 7182 - type checks for 'copy-object'Kartik Agaram2020-11-052-1/+412
|
* 7181 - type checks for 'address' instructionKartik Agaram2020-11-053-2/+595
|
* 7180Kartik Agaram2020-11-043-12/+173
| | | | | | | More bugfixes, now all apps are working. In the process of fixing the bugs in translating apps/browse, I found a typo in apps/tile that just happened to accidentally be compiling fine.
* 7179Kartik Agaram2020-11-042-0/+31
| | | | | | After this bugfix, apps/tile/ is now working. apps/browse/ is still failing.
* 7178 - type checks for 'compare' instructionKartik Agaram2020-11-042-1/+553
|
* 7177 - type checks for 'copy-to' instructionKartik Agaram2020-11-042-12/+400
|
* 7176 - type checks for 'copy' instructionKartik Agaram2020-11-043-104/+473
|
* 7174 - function returns should now be safeKartik Agaram2020-11-032-4/+197
|
* 7173Kartik Agaram2020-11-0312-12/+108
| | | | All tests passing again.
* 7172Kartik Agaram2020-11-031-1/+1
|
* 7171Kartik Agaram2020-11-031-1/+1
|
* 7170Kartik Agaram2020-11-031-0/+47
| | | | One more test.
* 7169Kartik Agaram2020-11-031-7/+88
| | | | | | | Now test-return-unavailable-value is passing, but test-convert-return-with-duplicate-values is failing. Time to think.
* 7168 - snapshotKartik Agaram2020-11-031-0/+93
| | | | | | | | 2 new tests: test-return-unavailable-value - currently failing test-convert-return-with-duplicate-values - currently passing I don't yet know how to make both pass.
* 7167Kartik Agaram2020-11-032-1/+74
|
* 7166Kartik Agaram2020-11-033-45/+170
|
* 7165Kartik Agaram2020-11-035-27/+94
| | | | | All tasks of https://github.com/akkartik/mu/issues/45#issuecomment-719990879 should now be complete.
* 7164Kartik Agaram2020-11-032-1/+112
|
* 7163 - first type checks for 'return' statementsKartik Agaram2020-11-032-2/+124
|
* 7161 - stop processing function outputsKartik Agaram2020-11-022-601/+109
| | | | | | Assignments to them will no longer work, and they can never be live variables. https://github.com/akkartik/mu/issues/45#issuecomment-719990879, task 3.
* 7160Kartik Agaram2020-11-022-133/+133
|
* 7159 - explicitly use 'return' everywhereKartik Agaram2020-11-0217-453/+405
| | | | https://github.com/akkartik/mu/issues/45#issuecomment-719990879, task 2.
* 7157Kartik Agaram2020-11-016-101/+96
|
* 7156Kartik Agaram2020-11-012-3/+6
|
* 7155Kartik Agaram2020-11-011-12/+12
| | | | apps/arith.mu compiling again.
* 7154Kartik Agaram2020-11-0112-369/+141
|
* 7153Kartik Agaram2020-11-012-3/+7
| | | | Bugfix in computing the label a return should jump to.
* 7152 - 'return' instructionKartik Agaram2020-11-012-1/+629
| | | | | | https://github.com/akkartik/mu/issues/45#issuecomment-719990879, task 1. We don't have checking for it yet. Soon.
* 7151Kartik Agaram2020-11-012-97/+46
| | | | Drop pending tests for the old plan of liveness analysis.
* 7148Kartik Agaram2020-10-312-5/+2
|
* 7145 - roll back to 7143Kartik Agaram2020-10-301-89/+174
|
* 7144 - tmp: redo checks for function outputsKartik Agaram2020-10-301-174/+89
| | | | | | | | | | | | | | | | | | | | | | | | | | | This isn't done, but an intermediate snapshot seems worth capturing. Back in March (commit 6082), I made a plan to check writes to function outputs using liveness analysis. I've been shying away from actually acting on this plan ever since. In recent weeks I've had this gap bite me three times. Returning to the problem now, I think I don't actually need to compute variable liveness. The compiler can, I think, do the same thing for output registers whether their variables are alive or dead. The new rule is this: Once a register gets a function output written to it, no local is popped into it. Instead of popping outer locals to the register, we simply increment the stack and keep going. Since the function output will continue to live on the vars stack past this point (see clean-up-block), any attempts to read shadowed variables will throw an error as usual. This rule is also now easy to explain to people, I think. "You wrote the function output. Now the register can't be used for anything else." It's really cool that this works (if it does). Another fruit from "Mu's lovely property."
* 7143Kartik Agaram2020-10-292-1/+1
| | | | Am I starting to have too much code duplication?
* 7142Kartik Agaram2020-10-292-0/+4
|
* 7141Kartik Agaram2020-10-292-4/+1
|
* 7140Kartik Agaram2020-10-291-0/+11
|
* 7139 - type-check compute-offsetKartik Agaram2020-10-292-13/+908
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-16 13:21:41 +0000