about summary refs log tree commit diff stats
path: root/079emit.subx
Commit message (Collapse)AuthorAgeFilesLines
* 6083Kartik Agaram2020-03-061-3/+3
|
* 5924Kartik Agaram2020-01-271-9/+9
|
* 5897 - rename comparison instructionsKartik Agaram2020-01-161-1/+1
| | | | | | | Signed and unsigned don't quite capture the essence of what the different combinations of x86 flags are doing for SubX. The crucial distinction is that one set of comparison operators is for integers and the second is for addresses.
* 5883 - drop the `ref` keywordKartik Agaram2020-01-121-7/+7
| | | | | | | | | | When I created it I was conflating two things: a) needing to refer to just the start, rather than the whole, and b) counting indirections. Both are kinda ill-posed. Now Mu will have just `addr` and `handle` types. Normal types will translate implicitly to `addr` types, while `handle` will always require explicit handling.
* 5876 - address -> addrKartik Agaram2020-01-031-1/+1
|
* 5851Kartik Agaram2020-01-011-3/+4
| | | | | | | | | | | | Rename a few scripts to be more consistent. I'm also starting to feel the urge to bud off `subx run` into its own program, say tools/emulate_x86. It doesn't really rely on the SubX notation at all. And then I could rename `subx translate` to `translate_subx_bootstrap`. Only problem: the commands in the Readme get verbose. But the Readme is gonna need surgery soon anyway to put translate_mu front and center.
* 5804Kartik Agaram2019-12-081-13/+13
| | | | | Try to make the comments consistent with the type system we'll eventually have.
* 5790Kartik Agaram2019-12-051-12/+12
| | | | | | Standardize conventions for labels within objects in the data segment. We're going to use this in a new tool.
* 5714Kartik Agaram2019-10-251-24/+12
| | | | Replace calculations of constants with labels.
* 5700Kartik Agaram2019-10-171-1/+1
|
* 5698Kartik Agaram2019-10-151-14/+14
| | | | Thanks Andrew Owen for reporting this typo.
* 5675 - move helpers from subx-common into layersKartik Agaram2019-09-191-0/+484
This undoes 5672 in favor of a new plan: Layers 000 - 099 are for running without syntax sugar. We use them for building syntax-sugar passes. Layers 100 and up are for running with all syntax sugar. The layers are arranged in approximate order so more phases rely on earlier layers than later ones. I plan to not use intermediate syntax sugar (just sigils without calls, or sigils and calls without braces) anywhere except in the specific passes implementing them.