| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 4072 | Kartik K. Agaram | 2017-10-16 | 1 | -3/+3 |
| | | |||||
| * | 4069 | Kartik K. Agaram | 2017-10-15 | 1 | -19/+19 |
| | | | | | subx: unconditional 'jump' | ||||
| * | 4067 | Kartik K. Agaram | 2017-10-15 | 1 | -1/+22 |
| | | | | | subx: 'mov' | ||||
| * | 4066 | Kartik K. Agaram | 2017-10-14 | 1 | -1/+1 |
| | | | | | | | I spent a while spelunking into the code generated by C compilers before realizing that ignoring the order of arguments for 'cmp' instructions clarifies everything. | ||||
| * | 4065 | Kartik K. Agaram | 2017-10-14 | 1 | -0/+45 |
| | | | | | | | subx: 'compare' Hopefully I've implemented the 'sense' of comparisons right.. | ||||
| * | 4064 | Kartik K. Agaram | 2017-10-14 | 1 | -14/+14 |
| | | |||||
| * | 4062 | Kartik K. Agaram | 2017-10-13 | 1 | -19/+19 |
| | | |||||
| * | 4059 | Kartik K. Agaram | 2017-10-13 | 1 | -72/+159 |
| | | |||||
| * | 4054 | Kartik K. Agaram | 2017-10-12 | 1 | -16/+16 |
| | | |||||
| * | 4052 | Kartik K. Agaram | 2017-10-12 | 1 | -0/+132 |