about summary refs log tree commit diff stats
path: root/subx/056trace.subx
Commit message (Collapse)AuthorAgeFilesLines
* .Kartik Agaram2019-06-081-3/+3
|
* .Kartik Agaram2019-06-081-1/+1
|
* fix stale docsKartik Agaram2019-06-081-11/+5
|
* snapshot of trace primitivesKartik Agaram2019-06-081-0/+346
|
* .Kartik Agaram2019-06-081-73/+61
|
* Fix stale `initialize-trace-stream`Kartik Agaram2019-06-081-3/+9
|
* start fleshing out trace support some moreKartik Agaram2019-06-051-5/+23
| | | | | I think the path to readable tests for survey.subx passes through white-box tests.
* 5074Kartik Agaram2019-04-101-3/+18
| | | | | | | | | | | | | Fail early when writing to a fake file runs out of space. Makes debugging tests easier. Reads from files, on the other hand, are only buffering to a temporary stream, so it makes sense to silently stop when they run out of space. In the process I uncovered a testing bug in pack.subx: I was missing a trailing space in the expected result, but the test still passed because the space was getting truncated. Being principled about aborting on overflow by default will help avoid such issues.
* 5059Kartik Agaram2019-04-051-1/+1
|
* 4981 - no, go back to 3 phasesKartik Agaram2019-02-181-8/+0
| | | | | | | | | | | | | Considering how much trouble a merge phase would be (commit 4978), it seems simpler to just add the extra syntax for controlling the entry point of the generated ELF binary. But I wouldn't have noticed this if I hadn't taken the time to write out the commit messages of 4976 and 4978. Even if we happened to already have linked list primitives built, this may still be a good idea considering that I'm saving quite a lot of code in duplicated entrypoints.
* 4973Kartik Agaram2019-02-151-5/+5
| | | | | Support immediate operands in the data segment in all the ways we support them in the code segment.
* 4961Kartik Agaram2019-02-141-7/+8
|
* 4951Kartik Agaram2019-02-031-2/+2
| | | | Cleaner way to compare streams in tests.
* 4949Kartik Agaram2019-02-021-0/+357