Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | 5600 | Kartik Agaram | 2019-08-31 | 21 | -91/+111 |
| | |||||
* | 5599 - sigils: support metadata in %reg and *reg | Kartik Agaram | 2019-08-31 | 2 | -3/+176 |
| | | | | | We already support metadata after *(...) No plans to support metadata _inside_ *(...) | ||||
* | 5598 | Kartik Agaram | 2019-08-31 | 1 | -2/+1 |
| | |||||
* | 5596 | Kartik Agaram | 2019-08-31 | 2 | -8/+12 |
| | |||||
* | 5595 - support ebp and esp in sigils | Kartik Agaram | 2019-08-31 | 2 | -0/+173 |
| | | | | The x86 instruction set carves out exceptions for these registers. | ||||
* | 5594 - rename 'desugar' to 'sigils' | Kartik Agaram | 2019-08-31 | 2 | -15/+16 |
| | | | | There's going to be multiple forms of syntax sugar going forward. | ||||
* | 5592 - switch register names to lowercase | Kartik Agaram | 2019-08-26 | 16 | -7413/+7413 |
| | |||||
* | 5591 | Kartik Agaram | 2019-08-26 | 11 | -0/+0 |
| | |||||
* | 5590 | Kartik Agaram | 2019-08-25 | 3 | -3/+3 |
| | |||||
* | 5589 | Kartik Agaram | 2019-08-25 | 11 | -9/+15 |
| | |||||
* | 5586 - bugfix: no desugar inside string literals | Kartik Agaram | 2019-08-25 | 10 | -434/+578 |
| | |||||
* | 5583 | Kartik Agaram | 2019-08-25 | 2 | -9/+181 |
| | | | | Clean up some missing error messages. | ||||
* | 5581 | Kartik Agaram | 2019-08-25 | 1 | -1/+3 |
| | |||||
* | . | Kartik Agaram | 2019-08-25 | 2 | -1/+183 |
| | |||||
* | Merge branch 'master' into desugar | Kartik Agaram | 2019-08-25 | 2 | -0/+62 |
|\ | |||||
| * | 5522 - example app: random number stream | Kartik Agaram | 2019-08-20 | 2 | -0/+62 |
| | | | | | | | | Turns out Mu's kernel isn't populating /dev/random correctly. | ||||
* | | desugar: more integration tests | Kartik Agaram | 2019-08-25 | 2 | -1/+206 |
| | | |||||
* | | desugar: code-generation seems complete | Kartik Agaram | 2019-08-25 | 2 | -5/+291 |
| | | |||||
* | | desugar: parsing seems complete | Kartik Agaram | 2019-08-25 | 2 | -37/+420 |
| | | |||||
* | | parsing *(reg-disp) | Kartik Agaram | 2019-08-25 | 2 | -0/+66 |
| | | |||||
* | | parsing *(reg+reg) | Kartik Agaram | 2019-08-25 | 2 | -21/+150 |
| | | | | | | | | | | | | | | | | | | Turns out there's an ambiguity even in this simple one-line language: when you see 'base+' you don't know whether the next token is the index or displacement. (Whereas a '-' would be unambiguous but is still not handled.) Fixing this ambiguity adds 15 instructions worth of complexity. | ||||
* | | parsing *(reg+disp) | Kartik Agaram | 2019-08-24 | 3 | -8/+549 |
| | | |||||
* | | . | Kartik Agaram | 2019-08-24 | 1 | -1/+1 |
| | | |||||
* | | integration tests for desugaring indirect mode | Kartik Agaram | 2019-08-24 | 2 | -2/+211 |
| | | | | | | | | They caught a logic error. | ||||
* | | integration tests for desugaring direct mode | Kartik Agaram | 2019-08-24 | 2 | -0/+212 |
| | | |||||
* | | use the results of parsing in emit-indirect-mode | Kartik Agaram | 2019-08-24 | 2 | -60/+33 |
| | | |||||
* | | parsing *(reg) | Kartik Agaram | 2019-08-24 | 2 | -0/+121 |
| | | |||||
* | | build out all variants for skipping whitespace | Kartik Agaram | 2019-08-24 | 11 | -0/+0 |
| | | | | | | | | skip {whitespace, non-whitespace} x {from stream, from slice} | ||||
* | | . | Kartik Agaram | 2019-08-23 | 1 | -0/+68 |
| | | | | | | | | This is pretty complex, but I may not need any more registers. | ||||
* | | . | Kartik Agaram | 2019-08-23 | 2 | -4/+14 |
| | | |||||
* | | . | Kartik Agaram | 2019-08-23 | 2 | -4/+12 |
| | | | | | | | | | | Some reorg as I realize I may have painted myself into a corner in this function. I have no registers left for the actual parsing. | ||||
* | | parsing *reg | Kartik Agaram | 2019-08-23 | 2 | -2/+102 |
| | | | | | | | | Isn't used yet, but baby steps. | ||||
* | | another error message | Kartik Agaram | 2019-08-23 | 2 | -1/+64 |
| | | |||||
* | | . | Kartik Agaram | 2019-08-23 | 1 | -3/+3 |
| | | |||||
* | | lexing complex expressions inside '*(...)' | Kartik Agaram | 2019-08-23 | 3 | -21/+442 |
| | | |||||
* | | couple of helpers for parsing expressions in parens | Kartik Agaram | 2019-08-22 | 2 | -0/+330 |
| | | |||||
* | | . | Kartik Agaram | 2019-08-16 | 1 | -2/+2 |
| | | |||||
* | | sketch of a plan to implement indirect mode | Kartik Agaram | 2019-08-16 | 2 | -2/+60 |
| | | |||||
* | | desugar: code-generate *reg | Kartik Agaram | 2019-08-16 | 2 | -1/+244 |
| | | |||||
* | | plan for supporting indirect mode | Kartik Agaram | 2019-08-16 | 2 | -22/+28 |
| | | | | | | | | | | | | | | | | | | | | | | It may superficially seem like there's a simpler approach: - emit '3/mod' or '0/mod' depending on whether the character is '%' or '*' - increment the start of word-slice - look up the register and emit the appropriate /rm32 But that won't work for 1/mod or 2/mod. We're doing a little bit of upfront planning. | ||||
* | | . | Kartik Agaram | 2019-08-16 | 1 | -4/+4 |
| | | |||||
* | | . | Kartik Agaram | 2019-08-16 | 1 | -1/+1 |
| | | |||||
* | | add desugar to CI | Kartik Agaram | 2019-08-13 | 1 | -0/+0 |
| | | |||||
* | | done implementing all variants of 'get' | Kartik Agaram | 2019-08-13 | 10 | -0/+0 |
| | | |||||
* | | done with get-or-stop | Kartik Agaram | 2019-08-13 | 10 | -0/+0 |
| | | |||||
* | | half-done testing get-or-stop | Kartik Agaram | 2019-08-13 | 10 | -0/+0 |
| | | | | | | | | | | | | Probably not needed for desugar; I'm just working through what we may replace the calls to 'get-slice' with if and when we decide to start focusing error messages and so writing tests for them. | ||||
* | | standardize test input/output/error streams | Kartik Agaram | 2019-08-13 | 14 | -170/+0 |
| | | |||||
* | | . | Kartik Agaram | 2019-08-13 | 10 | -0/+0 |
| | | |||||
* | | get desugar working on the commandline | Kartik Agaram | 2019-08-13 | 3 | -7/+54 |
| | | |||||
* | | . | Kartik Agaram | 2019-08-13 | 11 | -0/+0 |
| | |