about summary refs log tree commit diff stats
path: root/mu.md
Commit message (Collapse)AuthorAgeFilesLines
* rename grapheme to code-point-utf8Kartik K. Agaram2021-11-091-4/+4
| | | | | | Longer name, but it doesn't lie. We have no data structure right now for combining multiple code points. And it makes no sense for the notion of a grapheme to conflate its Unicode encoding.
* .Kartik K. Agaram2021-10-271-36/+36
|
* task: primitive statements vs function callsKartik K. Agaram2021-10-261-1/+7
|
* .Kartik K. Agaram2021-10-261-6/+10
|
* .Kartik K. Agaram2021-10-261-1/+1
|
* .Kartik K. Agaram2021-10-261-1/+1
|
* .Kartik K. Agaram2021-10-261-3/+2
|
* a few surprisingly nuanced tweaks to task 8Kartik K. Agaram2021-10-261-16/+18
| | | | Thanks sejo for the feedback.
* .Kartik K. Agaram2021-10-261-1/+1
|
* typo in tutorialKartik K. Agaram2021-10-261-2/+2
|
* task: floating-pointKartik K. Agaram2021-10-251-4/+21
| | | | | I'm almost ready to throw in the towel. Writing out the rules makes it obvious how hostile they are to most people.
* .Kartik K. Agaram2021-10-241-0/+2
|
* .Kartik K. Agaram2021-10-241-1/+4
|
* .Kartik K. Agaram2021-10-241-4/+5
|
* .Kartik K. Agaram2021-10-231-4/+5
|
* .Kartik K. Agaram2021-10-231-0/+4
|
* finally I can address sejo's feedback on shadow/clobberKartik K. Agaram2021-10-231-5/+12
|
* .Kartik K. Agaram2021-10-231-3/+3
|
* rewrite Mu referenceKartik K. Agaram2021-10-231-510/+382
|
* .Kartik K. Agaram2021-10-231-6/+6
|
* .Kartik K. Agaram2021-10-201-0/+1
|
* .Kartik K. Agaram2021-05-161-15/+18
|
* mu.subx: support bitwise notKartik K. Agaram2021-05-161-0/+3
|
* explicitly pass data disk to mainKartik K. Agaram2021-03-271-2/+3
|
* explicitly pass screen and keyboard to mainKartik K. Agaram2021-03-261-2/+25
|
* .Kartik K. Agaram2021-03-261-12/+3
|
* 7691Kartik Agaram2021-02-071-1/+16
|
* 7292 - mu.subx: loosen copy-byte checks a bitKartik Agaram2020-11-271-3/+3
| | | | | | | Without this there's no way to convert an int to a byte. And that feels too restrictive, and gives up a lot of safe things one might want to do with bytes. (Such as divide a number by 10 and emit the remainder as a byte.)
* 7286 - mu.subx: isolate bytes from previous valuesKartik Agaram2020-11-271-1/+2
|
* 7270Kartik Agaram2020-11-211-5/+5
|
* 7261 - mu.subx: array bounds-checking doneKartik Agaram2020-11-171-1/+1
|
* 7251Kartik Agaram2020-11-161-46/+49
|
* 7250Kartik Agaram2020-11-161-19/+11
|
* 7247Kartik Agaram2020-11-151-9/+60
|
* 7152 - 'return' instructionKartik Agaram2020-11-011-0/+4
| | | | | | https://github.com/akkartik/mu/issues/45#issuecomment-719990879, task 1. We don't have checking for it yet. Soon.
* 7028Kartik Agaram2020-10-141-4/+11
|
* 7027Kartik Agaram2020-10-141-2/+8
|
* 7026Kartik Agaram2020-10-141-1/+5
|
* 7024Kartik Agaram2020-10-141-35/+64
|
* 7023Kartik Agaram2020-10-141-2/+2
|
* 7022Kartik Agaram2020-10-141-2/+1
|
* 6957Kartik Agaram2020-10-051-0/+4
| | | | | | | | The final fix to the raytracing program involves rounding modes. It turns out x86 processors round floats by default, unlike C which has trained me to expect truncation. Rather than mess with the MXCSR register, I added another instruction for truncation. Now milestone 3 emits perfectly correct results.
* 6944Kartik Agaram2020-10-041-0/+3
|
* 6941 - detective story for the dayKartik Agaram2020-10-031-0/+5
|
* 6939Kartik Agaram2020-10-031-0/+6
|
* 6915 - a new family of Mu branch instructionsKartik Agaram2020-09-301-0/+9
| | | | | | The realization of commit 6916 means that we should be using jump-if-addr* after comparing floats. Which is super ugly. Let's create aliases to them called jump-if-float*.
* 6897Kartik Agaram2020-09-291-0/+7
|
* 6896Kartik Agaram2020-09-281-5/+90
| | | | Readme-driven development for Mu's floating-point operations.
* 6657Kartik Agaram2020-07-161-5/+6
|
* 6648 - bit-shift instructions in MuKartik Agaram2020-07-141-0/+7
| | | | I'm not happy with the names.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-22 01:20:25 +0000