Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | 5848 | Kartik Agaram | 2020-01-01 | 1 | -5/+5 |
| | |||||
* | 5847 - literal inputs | Kartik Agaram | 2019-12-31 | 16 | -1/+308 |
| | |||||
* | 5846 | Kartik Agaram | 2019-12-30 | 1 | -10/+10 |
| | |||||
* | 5845 | Kartik Agaram | 2019-12-30 | 1 | -0/+3 |
| | |||||
* | 5844 | Kartik Agaram | 2019-12-30 | 1 | -3/+3 |
| | | | | | Let's start putting r32 first in compare instructions that need it. Ordering there is quite subtle and of great import. | ||||
* | 5843 | Kartik Agaram | 2019-12-29 | 1 | -1/+1 |
| | |||||
* | 5842 | Kartik Agaram | 2019-12-29 | 1 | -0/+44 |
| | | | | | | Extremely crappy syntax highlighting for Emacs. I just can't wrap my head around elisp, and I'm inclined to blame elisp. Checking this off my todo list and moving on. | ||||
* | 5841 - rudimentary syntax highlighting for gedit | Kartik Agaram | 2019-12-28 | 1 | -0/+29 |
| | |||||
* | 5840 - syntax highlighting for nano (!!) | Kartik Agaram | 2019-12-28 | 1 | -0/+16 |
| | |||||
* | 5839 - colors for comments and string literals | Kartik Agaram | 2019-12-28 | 2 | -1/+32 |
| | |||||
* | 5838 - syntax highlighting for atom | Kartik Agaram | 2019-12-28 | 4 | -0/+63 |
| | |||||
* | 5837 - better colors for trace browser | Kartik Agaram | 2019-12-28 | 1 | -10/+25 |
| | |||||
* | 5836 | Kartik Agaram | 2019-12-28 | 1 | -1/+1 |
| | |||||
* | 5835 | Kartik Agaram | 2019-12-28 | 19 | -3787/+4858 |
| | |||||
* | 5834 | Kartik Agaram | 2019-12-27 | 2 | -3/+4 |
| | | | | Bugfix. | ||||
* | 5833 | Kartik Agaram | 2019-12-27 | 1 | -1/+1 |
| | |||||
* | 5832 - support for function outputs | Kartik Agaram | 2019-12-27 | 2 | -14/+138 |
| | | | | | | | | | | | We haven't implemented it yet, but there's now a design for how we check whether a function has written its output correctly. Functions must write to each output at the top level at least once, and never overwrite an output register in the top-level once it's been defined. This is conservative (it can be perfectly reasonable for functions to write the output, reuse the register for a temporary, and then write the output again) but easy to check. | ||||
* | 5831 | Kartik Agaram | 2019-12-27 | 2 | -27/+38 |
| | |||||
* | 5830 | Kartik Agaram | 2019-12-26 | 2 | -1/+5 |
| | | | | | Bugfix: statements defining a new register variable require an initializer instruction. | ||||
* | 5829 | Kartik Agaram | 2019-12-26 | 1 | -5/+15 |
| | |||||
* | 5828 - copy (mov) instructions | Kartik Agaram | 2019-12-26 | 2 | -22/+144 |
| | |||||
* | 5827 - give primitives one more bit of metadata | Kartik Agaram | 2019-12-26 | 2 | -4/+59 |
| | | | | | Copy (mov) instructions are unlike instructions we've encoded so far, in that their destination is not read. | ||||
* | 5826 - done with basic binary ops | Kartik Agaram | 2019-12-26 | 2 | -0/+197 |
| | |||||
* | 5825 - code-generation for add opcodes | Kartik Agaram | 2019-12-26 | 2 | -26/+158 |
| | |||||
* | 5824 - code-generation for all inc/dec opcodes | Kartik Agaram | 2019-12-26 | 2 | -2/+199 |
| | |||||
* | 5823 | Kartik Agaram | 2019-12-22 | 2 | -0/+55 |
| | |||||
* | 5822 | Kartik Agaram | 2019-12-22 | 2 | -3/+3 |
| | |||||
* | 5821 - now translating function arguments | Kartik Agaram | 2019-12-22 | 3 | -111/+157 |
| | | | | See test-convert-function-with-arg-and-body. | ||||
* | 5820 | Kartik Agaram | 2019-12-22 | 1 | -38/+177 |
| | | | | | | | | | | | One test failing. It took enough debugging just to get to the expected failure that it seems worth saving this snapshot. Saw some signs that I have to remember to zero-out allocated memory. We need a scalable solution for this. I think parse-var-with-type needs to be rewritten. Just added a test and a hacky fix for now. | ||||
* | 5819 | Kartik Agaram | 2019-12-22 | 3 | -3/+3 |
| | | | | Minor tweaks to stop wasting horizontal space in the trace. | ||||
* | 5818 | Kartik Agaram | 2019-12-22 | 4 | -16/+16 |
| | |||||
* | 5817 | Kartik Agaram | 2019-12-22 | 1 | -1/+4 |
| | |||||
* | 5816 - browse_trace bug fixed | Kartik Agaram | 2019-12-21 | 1 | -0/+1 |
| | |||||
* | 5815 | Kartik Agaram | 2019-12-21 | 1 | -4/+4 |
| | |||||
* | 5814 | Kartik Agaram | 2019-12-21 | 1 | -25/+25 |
| | |||||
* | 5813 | Kartik Agaram | 2019-12-21 | 1 | -2/+1 |
| | |||||
* | 5812 - debugging an ancient niggle in browse_trace | Kartik Agaram | 2019-12-21 | 1 | -6/+5 |
| | | | | | | | | The problem: when I hit 'G' to go to the bottom of the trace, if the bottom is visible on screen, the screen scrolls so the bottom of the trace is the bottom-most line on screen. But the cursor moves to where the trace used to end rather than the new location of the bottom of the trace (the bottom of the screen). | ||||
* | 5811 | Kartik Agaram | 2019-12-21 | 1 | -2/+2 |
| | |||||
* | 5810 | Kartik Agaram | 2019-12-09 | 3 | -24/+25 |
| | |||||
* | 5809 | Kartik Agaram | 2019-12-09 | 3 | -8/+9 |
| | |||||
* | 5808 | Kartik Agaram | 2019-12-09 | 2 | -89/+0 |
| | |||||
* | 5807 | Kartik Agaram | 2019-12-09 | 9 | -599/+673 |
| | |||||
* | 5806 | Kartik Agaram | 2019-12-09 | 79 | -16594/+16610 |
| | |||||
* | 5805 | Kartik Agaram | 2019-12-08 | 1 | -0/+12 |
| | |||||
* | 5804 | Kartik Agaram | 2019-12-08 | 68 | -1078/+1122 |
| | | | | | Try to make the comments consistent with the type system we'll eventually have. | ||||
* | 5803 | Kartik Agaram | 2019-12-07 | 15 | -27/+7 |
| | |||||
* | 5802 | Kartik Agaram | 2019-12-07 | 1 | -1/+1 |
| | | | | Fix CI. | ||||
* | 5801 - move `tangle` to `tools/` dir | Kartik Agaram | 2019-12-07 | 11 | -1096/+1087 |
| | |||||
* | 5800 - move `browse_trace` to `tools/` dir | Kartik Agaram | 2019-12-07 | 15 | -294/+1575 |
| | |||||
* | 5799 - move html-generation to `tools/` directory | Kartik Agaram | 2019-12-07 | 7 | -16/+7 |
| |