about summary refs log tree commit diff stats
path: root/subx/apps/pack.subx
Commit message (Collapse)AuthorAgeFilesLines
* 5105Kartik Agaram2019-04-161-172/+0
| | | | | Pull in a _different_ function than `next-word` (commit 5092) into a shared file between phases. Let's see how this goes.
* 5100Kartik Agaram2019-04-161-1/+1
|
* 5098Kartik Agaram2019-04-161-6/+6
|
* 5097Kartik Agaram2019-04-161-4/+5
|
* 5092Kartik Agaram2019-04-151-0/+245
| | | | | | | Realization: 'next-word' can't be reused in converting string literals, because it has to understand string literals. Let's just keep each phase self-contained.
* 5090Kartik Agaram2019-04-131-519/+103
| | | | | | | Start using the new newline escape in string literals everywhere. I could use it more aggressively, but it makes tests harder to read. So only one line of text per string for now.
* 5080Kartik Agaram2019-04-111-36/+20
|
* 5074Kartik Agaram2019-04-101-115/+149
| | | | | | | | | | | | | 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.
* 5072Kartik Agaram2019-04-101-15/+1
|
* 5064Kartik Agaram2019-04-071-3/+2
|
* 5059Kartik Agaram2019-04-051-23/+23
|
* 5058Kartik Agaram2019-04-051-245/+0
|
* 5057Kartik Agaram2019-04-051-1/+35
|
* 5054Kartik Agaram2019-04-031-4/+3
|
* 5053Kartik Agaram2019-04-031-40/+266
| | | | | | write-stream-buffered isn't a clean abstraction. Ignoring the 'read' index of a stream is a hack. It's just saving us the trouble of a rewind-stream. So make it a helper of pack.subx rather than part of the standard library.
* 5052Kartik Agaram2019-04-021-99/+127
|
* 5051 - done compiling SIB operandsKartik Agaram2019-04-021-3/+671
| | | | Done with pack.subx?!
* 5050 - compile ModR/M operandsKartik Agaram2019-04-021-1/+807
|
* 5049Kartik Agaram2019-04-021-100/+196
|
* 5048Kartik Agaram2019-04-011-12/+12
|
* 5047Kartik Agaram2019-04-011-3/+3
|
* 5046Kartik Agaram2019-04-011-72/+52
|
* 5045Kartik Agaram2019-04-011-8/+8
|
* 5044Kartik Agaram2019-04-011-3/+248
|
* 5043Kartik Agaram2019-04-011-0/+3
|
* 5042Kartik Agaram2019-03-311-33/+35
|
* 5041 - compile displacement operandsKartik Agaram2019-03-311-13/+565
|
* 5040 - compile immediate operandsKartik Agaram2019-03-301-16/+556
|
* 5039 - compile opcodesKartik Agaram2019-03-301-6/+1011
|
* 5038Kartik Agaram2019-03-291-11/+181
|
* 5037Kartik Agaram2019-03-291-13/+13
|
* 5036Kartik Agaram2019-03-291-34/+65
|
* 5034Kartik Agaram2019-03-291-50/+225
|
* 5029Kartik Agaram2019-03-281-49/+119
|
* 5028Kartik Agaram2019-03-281-5/+5
|
* 5027Kartik Agaram2019-03-271-11/+330
| | | | | | | | | Testing conversion of multiple lines in a data segment. Bugs fixed: 1. Stack issues in next-token helpers. 2. Needed to teach next-token to avoid newlines. 3. rewind-stream(line) before passing it to convert-code or convert-instruction.
* 5026Kartik Agaram2019-03-271-4/+4
|
* 5025Kartik Agaram2019-03-271-3/+7
|
* 5023Kartik Agaram2019-03-261-29/+422
| | | | | | | | | | | | | | | | Several bugs found after performing multiple loops through convert-data. This has been a general pattern: given how unsafe the x86 'language' is, the regular amount of testing with a single input doesn't really give sufficient confidence. Ever-present is the possibility that I forgot to pop something from the stack, either a spilled register or a local. Calling functions multiple times seems to help detect such bugs. So far I've been doing this extra level of testing implicitly when I build the next higher abstraction. But with `convert-data` the buck stopped, and much painful debugging ensued. One thing that would help is if `write` on streams didn't remain silent on overflow. But we actually need that sometimes, when streams are used as buffers.
* 5021 - done packing data segment?Kartik Agaram2019-03-231-14/+176
|
* 5020Kartik Agaram2019-03-231-2/+45
|
* 5019Kartik Agaram2019-03-231-3/+80
|
* 5018Kartik Agaram2019-03-231-7/+74
|
* 5017Kartik Agaram2019-03-221-5/+243
|
* 5014Kartik Agaram2019-03-211-106/+30
|
* 5013Kartik Agaram2019-03-201-29/+201
|
* 5012Kartik Agaram2019-03-201-1/+56
| | | | Add a bounds-check to `next-word`.
* 5010Kartik Agaram2019-03-201-1/+1
|
* 5009Kartik Agaram2019-03-201-12/+12
|
* 4996 - back on pack.subxKartik Agaram2019-03-081-233/+383
| | | | | | | | | Yet another redrawing of responsibilities between convert and its helpers. In the process I discovered a bug in `write-stream-buffered` which ended up taking me through a detour to extract `browse_trace` into its own tool. It turns out just having long buffers is enough to need browse_trace. Simple operations like clearing a stream swamp a flat view of the trace.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-08-20 19:27:30 +0000