diff --git a/docs/now/2026-10-06-published-update-s05-tri-27-conformance-to-the-emulator-fixed-in-ghash.md b/docs/now/2026-10-06-published-update-s05-tri-27-conformance-to-the-emulator-fixed-in-ghash.md new file mode 100644 index 0000000000..92de74e746 --- /dev/null +++ b/docs/now/2026-10-06-published-update-s05-tri-27-conformance-to-the-emulator-fixed-in-ghash.md @@ -0,0 +1,11 @@ +# NOW -- Update S05 TRI-27 conformance to the emulator fixed in gHashTag/trinity#1250 (published 2026-10-06) + +## A bee's work on #5614, published from `queen-5614` (Closes #5614) + +- The branch changes 4 file(s): `.trinity/seals/isa_Tri27Bytecode.json`, `.trinity/seals/isa_Tri27Machine.json`, `specs/isa/tri27_bytecode.t27`, `specs/isa/tri27_machine.t27`. +- `git diff --stat origin/master...queen-5614` reads: 4 files changed, 21 insertions(+), 4 deletions(-) +- This entry is written by the publisher, not by the bee. A pull request must + add exactly one `docs/now/` entry and a bee has no way to know that: its brief + names a boundary file and acceptance criteria, and `docs/now/` is neither. +- What this entry does NOT establish: that the work is correct. The gates on the + pull request judge that, and they are the same gates every other change meets. diff --git a/specs/isa/tri27_bytecode.t27 b/specs/isa/tri27_bytecode.t27 index 279f7e5292..069c8f374f 100644 --- a/specs/isa/tri27_bytecode.t27 +++ b/specs/isa/tri27_bytecode.t27 @@ -94,6 +94,13 @@ pub const FIXED_MEMORY_BYTES : u32 = 157464; pub const FIXED_CONSTANTS_HEADER_BYTES : u32 = 2; pub const FIXED_SIZE_SUM_MAX : u32 = 65535; +; --- Fixed upstream ------------------------------------------------------------------ +; The following findings from gHashTag/trinity#1164 were fixed in gHashTag/trinity#1250 (e7919fdc, 2026-10-02): +; - loader.load packs one code word per four-byte fetch unit at byte 12 + i*4, pc = 3 (#1166) - fixed by LOADER_PACKING fix +; - the writer and the loader agree on the twelve-byte header (#1167) - fixed by HEADER_AGREEMENT fix +; - the CONSTANTS parser reads id, then count, then count * 8 bytes (#1168) - fixed by CONSTANTS_LAYOUT fix +; These fixes are recorded for reference but the FINDINGS above remain pin-scoped to 976df517. + ; --- Rules ------------------------------------------------------------------------------------ pub fn magic_word(b0: u32, b1: u32, b2: u32, b3: u32) -> u32 { diff --git a/specs/isa/tri27_machine.t27 b/specs/isa/tri27_machine.t27 index 339199b6d6..fad75cbe06 100644 --- a/specs/isa/tri27_machine.t27 +++ b/specs/isa/tri27_machine.t27 @@ -121,6 +121,16 @@ pub const IMM_SHIFT : u32 = 17; pub const IMM_MASK : u32 = 32767; pub const IMM_SIGN : u32 = 16384; +; --- Fixed upstream ------------------------------------------------------------------ +; The following findings from gHashTag/trinity#1164 were fixed in gHashTag/trinity#1250 (e7919fdc, 2026-10-02): +; - CALL pushes the address of the instruction after it (#1165) - fixed by CALL_RETURN_ADDRESS fix +; - loader.load packs one code word per four-byte fetch unit at byte 12 + i*4, pc = 3 (#1166) - fixed by LOADER_PACKING fix +; - the writer and the loader agree on the twelve-byte header (#1167) - fixed by HEADER_AGREEMENT fix +; - the CONSTANTS parser reads id, then count, then count * 8 bytes (#1168) - fixed by CONSTANTS_LAYOUT fix +; - the modulus labels say 3^9 (#1169) - fixed by MODULUS_LABELS fix +; - SACR is an immediate instruction in the decoder, so its mode round-trips (#1170) - fixed by SACR_IMMEDIATE fix +; These fixes are recorded for reference but the FINDINGS above remain pin-scoped to 976df517. + ; --- Registers and operands ----------------------------------------------------------------- pub fn registers_valid(dst: u32, src1: u32, src2: u32, cond: u32) -> bool {