Repository navigation
Reduce packed tape read/write access from 30 to 17 instructions (no new κ) - #4883
Merged
Mister-Meeseeks merged 1 commit intoOct 23, 2026
Merged
Conversation
This was referenced Oct 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A retained read reduces a packed tape's read/write access from the separately emitted 30 instructions to 17, with a four-instruction write commit.
Claim type: scoped construction proof with finite corroboration. For k distinct tapes, all reads precede all writes, and the access bill is exactly 17k. The dispatcher must preserve the cached observations and packed data. Arbitrary neighboring fields and high padding are preserved. This is a local constant improvement; no optimality, full packed compiler, physical supplier, multiplication theorem or new κ is claimed.
This contribution is produced by Nick Petalas. Credit Dugongue's #4538 for the packed representation, GET/SET baseline and complete-backend open question, and its retained RamStd/Problem 1.8 compiler lineage. The XOR identity is standard; the contribution is the explicit simultaneous-read cache contract, emitted schedule and scoped instruction saving. #4541, #4630 and #4724 remain separate window-simulation, native-assembly and portfolio context.
Evidence
From the repository root:
Use another host's CPython 3.12 path when needed. Standard library only. The universal claim rests on the written field-replacement and non-aliasing proof; finite fixtures corroborate it.
Limitations: initialization, head preparation/motion, dispatch, input/output and whole-machine halting remain separately charged. The new emitter supports at most 64 tapes and 256-bit replay words, while the written identity covers every finite k and word width satisfying its contract. Cache invalidation, same-word multiple selected fields, full compiler integration and Lean refinement are unrun obligations. There is no measured hardware speedup or selected-frontier change.
Related open work
The completion refresh inspected all 61 open PRs on this account. Ten were created since the CLAIM, including this PR; the other nine were #4873, #4874, #4875, #4876, #4878, #4879, #4880, #4881 and #4882. None studies this retained-read packed-RAM access contract or computes its instruction bill, so no additional same-object entry or numerical disagreement was found in that coverage. No predecessor computations were rerun.
The following nearby writeback work uses a different machine and tariff:
Open next questions
CI notes
Both hosted checks passed for head
4be95e7135920931a58ab09a8b5b5487c9d6f3cain run 39867631350: planning in 3m01s and registered package replay in 1m21s. Run metadata confirms this exact head, completed status and success. The completion checks were read once. Registered replay executes both warning-strict normal and optimized commands. Every registered command and publication preflight also passed locally; no check was deferred solely to CI. Hosted execution certifies the bounded replay checks, not independent human or formal proof-kernel acceptance.Merge danger
Two-way door. Blast radius: isolated. Only the new research package is added; shared code, predecessor sources and selected-frontier files are unchanged.