| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 7292 - mu.subx: loosen copy-byte checks a bit | Kartik Agaram | 2020-11-27 | 1 | -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 values | Kartik Agaram | 2020-11-27 | 1 | -1/+2 |
| | | |||||
| * | 7270 | Kartik Agaram | 2020-11-21 | 1 | -5/+5 |
| | | |||||
| * | 7261 - mu.subx: array bounds-checking done | Kartik Agaram | 2020-11-17 | 1 | -1/+1 |
| | | |||||
| * | 7251 | Kartik Agaram | 2020-11-16 | 1 | -46/+49 |
| | | |||||
| * | 7250 | Kartik Agaram | 2020-11-16 | 1 | -19/+11 |
| | | |||||
| * | 7247 | Kartik Agaram | 2020-11-15 | 1 | -9/+60 |
| | | |||||
| * | 7152 - 'return' instruction | Kartik Agaram | 2020-11-01 | 1 | -0/+4 |
| | | | | | | | https://github.com/akkartik/mu/issues/45#issuecomment-719990879, task 1. We don't have checking for it yet. Soon. | ||||
| * | 7028 | Kartik Agaram | 2020-10-14 | 1 | -4/+11 |
| | | |||||
| * | 7027 | Kartik Agaram | 2020-10-14 | 1 | -2/+8 |
| | | |||||
| * | 7026 | Kartik Agaram | 2020-10-14 | 1 | -1/+5 |
| | | |||||
| * | 7024 | Kartik Agaram | 2020-10-14 | 1 | -35/+64 |
| | | |||||
| * | 7023 | Kartik Agaram | 2020-10-14 | 1 | -2/+2 |
| | | |||||
| * | 7022 | Kartik Agaram | 2020-10-14 | 1 | -2/+1 |
| | | |||||
| * | 6957 | Kartik Agaram | 2020-10-05 | 1 | -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. | ||||
| * | 6944 | Kartik Agaram | 2020-10-04 | 1 | -0/+3 |
| | | |||||
| * | 6941 - detective story for the day | Kartik Agaram | 2020-10-03 | 1 | -0/+5 |
| | | |||||
| * | 6939 | Kartik Agaram | 2020-10-03 | 1 | -0/+6 |
| | | |||||
| * | 6915 - a new family of Mu branch instructions | Kartik Agaram | 2020-09-30 | 1 | -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*. | ||||
| * | 6897 | Kartik Agaram | 2020-09-29 | 1 | -0/+7 |
| | | |||||
| * | 6896 | Kartik Agaram | 2020-09-28 | 1 | -5/+90 |
| | | | | | Readme-driven development for Mu's floating-point operations. | ||||
| * | 6657 | Kartik Agaram | 2020-07-16 | 1 | -5/+6 |
| | | |||||
| * | 6648 - bit-shift instructions in Mu | Kartik Agaram | 2020-07-14 | 1 | -0/+7 |
| | | | | | I'm not happy with the names. | ||||
| * | 6645 - heap allocations in Mu | Kartik Agaram | 2020-07-13 | 1 | -0/+16 |
| | | | | | | | | | - allocate var - populate var, n Both rely on the type of `var` to compute the size of the allocation. No need to repeat the name of the type like in C, C++ or Java. | ||||
| * | 6642 | Kartik Agaram | 2020-07-12 | 1 | -10/+10 |
| | | |||||
| * | 6640 | Kartik Agaram | 2020-07-12 | 1 | -194/+194 |
| | | | | | Re-sync markdown files with mu-normie fork. | ||||
| * | 6621 | Kartik Agaram | 2020-07-06 | 1 | -0/+5 |
| | | |||||
| * | 6620 | Kartik Agaram | 2020-07-06 | 1 | -1/+1 |
| | | |||||
| * | 6619 | Kartik Agaram | 2020-07-06 | 1 | -1/+1 |
| | | |||||
| * | 6618 - new docs | Kartik Agaram | 2020-07-06 | 1 | -0/+456 |