Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | bugfix in mandelbrot-fixed | Kartik K. Agaram | 2021-05-09 | 1 | -13/+19 |
| | | | | | | | | Thanks to comparing regular ints with fixed-point ints, I was computing iterations for many screenfuls of pixels to the right of the current one. (Y-axis behaved similarly, but there it was just doing other work instead of busy-looping forever. If you don't have anything else to do, it doesn't matter what you do.) | ||||
* | . | Kartik K. Agaram | 2021-05-09 | 2 | -31/+31 |
| | | | | | Yet another step in the slow divergence of survey_baremetal from its survey_elf roots. | ||||
* | . | Kartik Agaram | 2021-05-09 | 1 | -7/+43 |
| | |||||
* | . | Kartik Agaram | 2021-05-09 | 2 | -6/+6 |
| | |||||
* | . | Kartik Agaram | 2021-05-09 | 4 | -4/+4 |
| | |||||
* | . | Kartik Agaram | 2021-05-09 | 4 | -352/+372 |
| | |||||
* | . | Kartik Agaram | 2021-05-09 | 2 | -34/+42 |
| | |||||
* | mandelbrot: streamline exposition | Kartik Agaram | 2021-05-09 | 4 | -283/+254 |
| | |||||
* | . | Kartik Agaram | 2021-05-09 | 2 | -195/+197 |
| | |||||
* | . | Kartik Agaram | 2021-05-08 | 2 | -0/+499 |
| | |||||
* | mandelbrot set in fixed-point | Kartik K. Agaram | 2021-05-08 | 2 | -15/+239 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-08 | 1 | -1/+1 |
| | |||||
* | support checking overflow flag everywhere | Kartik K. Agaram | 2021-05-08 | 8 | -9/+517 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-08 | 1 | -1/+1 |
| | |||||
* | initial, monochrome mandelbrot set | Kartik K. Agaram | 2021-05-08 | 1 | -0/+149 |
| | |||||
* | A 'bowboard', a chessboard of rainbow circles | Kartik K. Agaram | 2021-05-08 | 1 | -23/+31 |
| | | | | Compare with (chessboard screen 256) | ||||
* | a full-circle rainbow | Kartik K. Agaram | 2021-05-08 | 2 | -3/+30 |
| | |||||
* | new shell macro: do | Kartik K. Agaram | 2021-05-07 | 1 | -2/+3 |
| | |||||
* | always check for null in 'index' instructions | Kartik K. Agaram | 2021-05-07 | 6 | -95/+132 |
| | |||||
* | all apps working again after null get check | Kartik K. Agaram | 2021-05-07 | 2 | -2/+34 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-07 | 2 | -39/+39 |
| | |||||
* | always check for null in 'get' instructions | Kartik K. Agaram | 2021-05-07 | 5 | -14/+51 |
| | |||||
* | a little bit more information when lookup fails | Kartik K. Agaram | 2021-05-07 | 1 | -1/+31 |
| | | | | | | Basically this should never, ever happen until I start reclaiming heap memory. I believe the only reason it happens is unprotected writes to address 0 or thereabouts. | ||||
* | an often-overflowing stream when running brcircle | Kartik K. Agaram | 2021-05-07 | 2 | -1/+3 |
| | | | | We really need to systematically check our trace streams. | ||||
* | . | Kartik K. Agaram | 2021-05-07 | 2 | -6/+8 |
| | |||||
* | some boot-time heartbeat messages | Kartik K. Agaram | 2021-05-07 | 2 | -1/+20 |
| | | | | This will help us with some common debug scenarios. | ||||
* | . | Kartik K. Agaram | 2021-05-07 | 1 | -19/+19 |
| | |||||
* | clean up all definitions | Kartik K. Agaram | 2021-05-07 | 1 | -21/+20 |
| | |||||
* | clean up chessboard | Kartik K. Agaram | 2021-05-07 | 2 | -11/+15 |
| | | | | | We still benefit from some helpers here because of the unrolling and multiple calls to helpers. | ||||
* | clean up read_line | Kartik K. Agaram | 2021-05-07 | 1 | -9/+6 |
| | |||||
* | clean up Bresenham line-drawing | Kartik K. Agaram | 2021-05-07 | 2 | -26/+54 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-07 | 1 | -6/+6 |
| | |||||
* | no, we need hline1 for fill_rect | Kartik K. Agaram | 2021-05-07 | 1 | -8/+10 |
| | |||||
* | clean up hline and vline | Kartik K. Agaram | 2021-05-07 | 1 | -10/+10 |
| | |||||
* | starting to implement first macros | Kartik K. Agaram | 2021-05-07 | 4 | -0/+20 |
| | | | | | | | | | | | | | | | Another commit, another bugfix. Some snippets from my currently exploding todo list: - always investigate lookup errors immediately. Beyond the root cause, they should never happen at the moment, while we aren't reclaiming memory. we should always return a more precise error message. Usually involving null pointer checks. - on abort, print out stack trace - emit mapping of labels to addresses during survey - store a mapping of symbols somewhere in the code image - stop allocating 1KB per token; expand space for tokens as needed | ||||
* | give up on nested backquotes for now | Kartik K. Agaram | 2021-05-07 | 2 | -7/+82 |
| | |||||
* | macros almost done | Kartik K. Agaram | 2021-05-06 | 1 | -23/+69 |
| | | | | Just one case left: macros within unquote. | ||||
* | some more cases | Kartik K. Agaram | 2021-05-06 | 1 | -11/+60 |
| | |||||
* | first passing test for macroexpand | Kartik K. Agaram | 2021-05-06 | 6 | -41/+249 |
| | | | | | | | | In the process I spent a long time tracking down a stray TODO in 108write.subx that I thought would abort but didn't since the switch to baremetal. Then after I reintroduced that assertion I had to go track down a bunch of buffer sizes. Stream sizes continue to be a huge mess. | ||||
* | . | Kartik K. Agaram | 2021-05-06 | 1 | -1/+1 |
| | |||||
* | more paranoia in shell/globals.mu | Kartik K. Agaram | 2021-05-06 | 1 | -0/+48 |
| | |||||
* | shell: macroexpand outermost call | Kartik K. Agaram | 2021-05-06 | 2 | -1/+65 |
| | |||||
* | literal macros | Kartik K. Agaram | 2021-05-06 | 1 | -0/+28 |
| | | | | | | | | | | | Current plan: - some way to define macros. For now: (def f (litmac litfn () (a b) `(+ ,a , b))) - macroexpand will expand calls by passing them through the cdr (f 3 4) macroexpand: ((litfn () (a b) `(+ ,a ,b)) 3 4) => (+ 3 4) eval: (+ 3 4) => 7 | ||||
* | . | Kartik K. Agaram | 2021-05-06 | 1 | -2/+15 |
| | |||||
* | back to macros; switch macroexpand to operate in place | Kartik K. Agaram | 2021-05-06 | 2 | -20/+9 |
| | |||||
* | belatedly migrate stale example definitions | Kartik K. Agaram | 2021-05-06 | 4 | -93/+99 |
| | | | | | Also bare-bones syntax highlighting for .limg files. Doesn't work when .limg file is first file opened with Vim. | ||||
* | . | Kartik K. Agaram | 2021-05-06 | 1 | -4/+21 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-04 | 2 | -0/+41 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-04 | 2 | -3/+25 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-04 | 1 | -1/+1 |
| |