evocation/hex.e, branch v3.0Call forth the blue-green flame of computation from the universe, weave its energies into a fabric, that we may share our blood with it.
http://code.irenes.space/evocation/atom?h=v3.02026-09-21T07:37:17+00:00mark a couple labels in hex.e as non-offset2026-09-21T07:37:17+00:00Irene Knappireneista@irenes.space2026-09-21T07:37:17+00:00urn:sha1:53cb8ad78845f95383b0a253eeef05cc76364743
and rebuild hex.hex with the latest features
Force-Push: yes
Change-Id: Ic96c1ff6b06d2ecfb08a5c6829206460c0cdcf95
add an implicit way to define suffix comments2026-09-09T09:14:35+00:00Irene Knappireneista@irenes.space2026-09-09T09:14:35+00:00urn:sha1:157f657585bf536149effbc1a0a4f51b61a4ea35
and make the explicit way more versatile (allowing zero length)
this required hooking the lexer at a pretty low level, but it worked out fine
Force-Push: yes
Change-Id: Icdbe233fbf9d4cf07cb8d03975eed3b4f7b620aa
provide a #swap operation in comment templates2026-09-09T07:07:25+00:00Irene Knappireneista@irenes.space2026-09-09T07:02:32+00:00urn:sha1:f74440d8090e6b15abe47f71b169058e7b151447
and use it in a couple places in amd64.e where it's needed
Change-Id: Id73dcd13f08c03aa02ac09e45ab034fcd90f2569
Force-Push: yes
bubblesort the metadata entries during postprocessing2026-09-08T22:41:37+00:00Irene Knappireneista@irenes.space2026-09-08T22:41:37+00:00urn:sha1:70ce12dc055bfead28d61225ea9bcb5b11a6c242
since we do this here, we no longer need to worry about doing it during initial entry creation, so that's good. that had been on the mental "maybe later" checklist for a while.
the various innovations in entry processing now make it possible to pass
through most of the formatting in hex.e, so that's done now (suffix comments that aren't instruction decodings still need to be made to work)
there's also a new entry type which will be part of the comment parameter system. that's not fully working yet, but this was a bunch of really subtle debugging, so it makes a good spot to checkpoint at.
Force-Push: yes
Change-Id: I2aff7276368eaad7e5c280a58834605e294dcd74
the hex dump now prints trailing messages at the end of the data2026-09-08T12:05:07+00:00Irene Knappireneista@irenes.space2026-09-08T12:04:37+00:00urn:sha1:6f76a3a291d1a895e3e5cd36103fb4c4199825e1
Force-Push: yes
Change-Id: I71930b088c176ade6a0bf7aaecb46bdecb0636ad
add indentation and blank lines as magic-comment features2026-09-08T06:53:55+00:00Irene Knappireneista@irenes.space2026-09-08T06:53:55+00:00urn:sha1:05e59d02e76a1eed55f04f63257a7bb65326bcb0
the output is really starting to look like something!
Force-Push: yes
Change-Id: Ic41c8b1702d884ff89693a86d457af7cc752aa86
add tracing of the latest output point in packstring2026-09-08T06:04:15+00:00Irene Knappireneista@irenes.space2026-09-08T06:04:15+00:00urn:sha1:06ce6d8b66db0a274e36d05f8a9b470455b84728
this is necessary because packstring isn't implemented in terms of pack8, unlike packalign
also add a bunch more magic comments to hex.e, which would be in the wrong place without the semantic change
Force-Push: yes
Change-Id: I422b8d00a07568be5113e005fddaeab82f5ca731
it spits out correct hex2026-06-13T03:55:32+00:00Irene Knappireneista@irenes.space2026-06-13T03:55:32+00:00urn:sha1:9eb7d0fabb2a786d2aa9f56244360afb381e7c18
no comments yet, of course. also no way to run it on evoke itself yet, due to the buffer thing.
Force-Push: yes
Change-Id: Ia1d7cc06bd3da59a5d272e1c04606c25d46acee5
added a program, hex.e, which will be the bootstrap strategy2026-05-25T02:31:20+00:00Irene Knappireneista@irenes.space2026-05-25T02:31:20+00:00urn:sha1:db39fec4b6acdef6e9e03a69d2727a2ae4bcb5ba
also added some instructions it needed
Force-Push: yes
Change-Id: Ia35280e2696167eb0662a5c3a9dc47840438da56