| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 5924 | Kartik Agaram | 2020-01-27 | 64 | -891/+891 |
| | | |||||
| * | 5923 - start work on code-generation for 'var' | Kartik Agaram | 2020-01-27 | 2 | -3/+45 |
| | | |||||
| * | 5922 | Kartik Agaram | 2020-01-26 | 1 | -5556/+5674 |
| | | |||||
| * | 5921 | Kartik Agaram | 2020-01-26 | 2 | -5/+130 |
| | | |||||
| * | 5920 | Kartik Agaram | 2020-01-26 | 2 | -29/+57 |
| | | |||||
| * | 5919 | Kartik Agaram | 2020-01-26 | 2 | -24/+0 |
| | | |||||
| * | 5918 | Kartik Agaram | 2020-01-26 | 2 | -22/+11 |
| | | |||||
| * | 5917 | Kartik Agaram | 2020-01-22 | 1 | -4299/+4293 |
| | | |||||
| * | 5916 | Kartik Agaram | 2020-01-22 | 2 | -3/+3 |
| | | |||||
| * | 5915 | Kartik Agaram | 2020-01-21 | 1 | -3/+3 |
| | | |||||
| * | 5914 | Kartik Agaram | 2020-01-21 | 1 | -3/+1 |
| | | |||||
| * | 5913 | Kartik Agaram | 2020-01-20 | 1 | -6/+0 |
| | | |||||
| * | 5912 | Kartik Agaram | 2020-01-20 | 1 | -4115/+4450 |
| | | |||||
| * | 5911 - support for compound types | Kartik Agaram | 2020-01-20 | 2 | -15/+13 |
| | | |||||
| * | 5910 | Kartik Agaram | 2020-01-20 | 1 | -2/+1 |
| | | | | | | Trace browser: Don't let the background color get too light, and cycle back to darker shades so I'm not squinting at low depths. | ||||
| * | 5909 | Kartik Agaram | 2020-01-20 | 1 | -18/+62 |
| | | | | | Draft 5. | ||||
| * | 5908 | Kartik Agaram | 2020-01-20 | 1 | -4/+6 |
| | | | | | | Now parse-type passes, but some outer test is failing. The result is not being consumed right by `type-equal?`. | ||||
| * | 5907 | Kartik Agaram | 2020-01-20 | 1 | -10/+24 |
| | | | | | | | Draft 3. Getting close. Now the tree structure seems right. | ||||
| * | 5906 | Kartik Agaram | 2020-01-20 | 1 | -3/+35 |
| | | | | | Draft 2. | ||||
| * | 5905 | Kartik Agaram | 2020-01-20 | 1 | -84/+329 |
| | | | | | | | | Draft of my first, incorrect attempt at parsing s-expressions. No matter how many times I've done this, I never get it right the first time. | ||||
| * | 5904 | Kartik Agaram | 2020-01-19 | 3 | -12/+12 |
| | | |||||
| * | 5903 | Kartik Agaram | 2020-01-19 | 3 | -1579/+1581 |
| | | |||||
| * | 5902 | Kartik Agaram | 2020-01-19 | 1 | -6/+6 |
| | | |||||
| * | 5901 | Kartik Agaram | 2020-01-19 | 14 | -1147/+1176 |
| | | |||||
| * | 5900 | Kartik Agaram | 2020-01-19 | 1 | -0/+16 |
| | | |||||
| * | 5899 | Kartik Agaram | 2020-01-19 | 2 | -4/+11 |
| | | |||||
| * | 5898 - strengthen slice-empty? check | Kartik Agaram | 2020-01-19 | 15 | -7/+36 |
| | | | | | | | | | | | | Anytime we create a slice, the first check tends to be whether it's empty. If we handle ill-formed slices here where start > end, that provides a measure of safety. In the Mu translator (mu.subx) we often check for a trailing ':' or ',' and decrement slice->end to ignore it. But that could conceivably yield ill-formed slices if the slice started out empty. Now we make sure we never operate on such ill-formed slices. | ||||
| * | 5897 - rename comparison instructions | Kartik Agaram | 2020-01-16 | 114 | -1140/+1124 |
| | | | | | | | | Signed and unsigned don't quite capture the essence of what the different combinations of x86 flags are doing for SubX. The crucial distinction is that one set of comparison operators is for integers and the second is for addresses. | ||||
| * | 5896 | Kartik Agaram | 2020-01-16 | 2 | -22/+22 |
| | | |||||
| * | 5895 | Kartik Agaram | 2020-01-16 | 2 | -22/+22 |
| | | |||||
| * | 5894 | Kartik Agaram | 2020-01-16 | 3 | -10/+10 |
| | | |||||
| * | 5893 | Kartik Agaram | 2020-01-14 | 28 | -3744/+3665 |
| | | |||||
| * | 5892 | Kartik Agaram | 2020-01-14 | 6 | -10/+4 |
| | | |||||
| * | 5891 | Kartik Agaram | 2020-01-14 | 1 | -0/+20 |
| | | |||||
| * | 5890 | Kartik Agaram | 2020-01-14 | 2 | -2/+2 |
| | | |||||
| * | 5889 | Kartik Agaram | 2020-01-14 | 12 | -4847/+5009 |
| | | |||||
| * | 5888 | Kartik Agaram | 2020-01-14 | 1 | -228/+222 |
| | | |||||
| * | 5887 - reorganize library | Kartik Agaram | 2020-01-14 | 21 | -9/+16 |
| | | | | | | | | Layers 0-89 are used in self-hosting SubX. Layers 90-99 are not needed for self-hosting SubX, and therefore could use transitional levels of syntax sugar. Layers 100 and up use all SubX syntax sugar. | ||||
| * | 5886 | Kartik Agaram | 2020-01-12 | 3 | -13/+14 |
| | | |||||
| * | 5885 | Kartik Agaram | 2020-01-12 | 2 | -62/+231 |
| | | | | | Finalize design for type trees. | ||||
| * | 5884 | Kartik Agaram | 2020-01-12 | 46 | -6406/+6392 |
| | | |||||
| * | 5883 - drop the `ref` keyword | Kartik Agaram | 2020-01-12 | 41 | -384/+365 |
| | | | | | | | | | | | When I created it I was conflating two things: a) needing to refer to just the start, rather than the whole, and b) counting indirections. Both are kinda ill-posed. Now Mu will have just `addr` and `handle` types. Normal types will translate implicitly to `addr` types, while `handle` will always require explicit handling. | ||||
| * | 5882 | Kartik Agaram | 2020-01-10 | 1 | -3/+1 |
| | | |||||
| * | 5881 | Kartik Agaram | 2020-01-10 | 9 | -4901/+4983 |
| | | |||||
| * | 5880 | Kartik Agaram | 2020-01-10 | 9 | -9/+9 |
| | | |||||
| * | 5879 | Kartik Agaram | 2020-01-10 | 2 | -10/+99 |
| | | |||||
| * | 5878 | Kartik Agaram | 2020-01-03 | 2 | -270/+217 |
| | | | | | | The current prototype doesn't really use floating point; drop the guardrails there. | ||||
| * | 5877 | Kartik Agaram | 2020-01-03 | 2 | -4/+4 |
| | | |||||
| * | 5876 - address -> addr | Kartik Agaram | 2020-01-03 | 110 | -716/+716 |
| | | |||||
| * | 5875 | Kartik Agaram | 2020-01-02 | 16 | -56/+207 |
| | | |||||