Skip to content

Select enclosing TP6 procedures by explicit bounded TPU9 entry - #4

Merged
janrysavy merged 1 commit into
mainfrom
review/tpu-explicit-entry-20260926
Sep 26, 2026
Merged

janrysavy merged 1 commit into
mainfrom
review/tpu-explicit-entry-20260926

Conversation

@janrysavy

Copy link
Copy Markdown
Owner

The fresh Pyro numeric-display reconstruction emits its two nested helpers before its enclosing routine (code offsets 0,50,131). The existing earliest-entry-only API cannot select the actual target without callers writing their own decoder.

Add optional keyword-only code_offset to primary_span/primary_routine. It must name an exact declared code-section-relative entry; no arbitrary byte offsets, byte-pattern search, fallback to other entries, or reads beyond the owning entry/block. Existing default behavior and error messages remain unchanged.

Twelve new regression cases failed before implementation and all pass after it, covering later-entry selection, invalid types/offsets, undeclared literal prologues, adjacent returns, cumulative block geometry, aliases and failed selected entries. Local focused suite: 43 passed (31 existing + 12 new). No licensed binaries included.

Consumer validation: dostools PR #11 has freshly compiled the enclosing 156-byte Pyro routine with TP6 inside PyPC-MCP, with four real wrong-source controls; parent integration will use this explicit selector instead of the temporary probe decoder.

@janrysavy
janrysavy merged commit b53a1be into main Sep 26, 2026
1 check passed
@janrysavy
janrysavy deleted the review/tpu-explicit-entry-20260926 branch September 26, 2026 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant