rpg_shape.compilerOrigin: lane Co finds no public layout for the statement_marker refusal; nothing changes #811

Manually merged
binjovi-bot merged 1 commit from lane-co-origin-20261117 into trunk 2026-11-17 05:50:23 +00:00
Owner

rpg_shape.compilerOrigin: lane Co finds no public layout for the statement_marker refusal; nothing changes

Negative result. No source, test or emit byte changes in this pull request.

Question: which public procedure layouts reach compilerOrigin s01
(statement_marker, the procedure does not open with statement 2100000001 and
close with 2100000002), while carrying a compiler-originated marker that the
shape marker, entry procedure and INIT call tests would accept?

Measured on a Debug build of the branch base (fba2d222),
SOURCERER_TRACE_REFUSALS=1, over every public archive.savf under
src/testdata/savf except LEMONADE (no private, held-out or exam material):

  • Every procedure that carries 2100000001 or 2100000002 (23 archives: ACCESS,
    DSPLY, MONITOR, TSTRIP, TSTRIP-STRIPPED and the EXPERIMENTS probes
    format-base, format-rename, gotos-static, shared-io-full, shared-io-none and
    others) lists 2100000001 first and 2100000002 last among its numbered
    statements. The groups outside the pair are statement none (the unnumbered
    instructions before the first and after the last numbered statement), not
    numbered statements in between. No procedure has either marker at another
    position, and none has only one of the pair.
  • No archive with a marker procedure appears among the archives that fire
    s01. The refusal never reaches a layout that has the marker.
  • The archives that fire s01 (FLOW, OPS, INIT and others) carry no 2100000001
    or 2100000002 at all: their main procedure starts at the source-statement
    marker 1000001 and ends at 1000002 (OPTION(*SRCSTMT)). That is a
    different marker pair, not a displaced one. Accepting it would accept a
    marker by number alone, which the brief rules out, and those statements are
    read as source, not as compiler origin.

So the placement test has no public case to widen to, and a red test cannot be
written on a public probe. compilerOrigin, compilerProved and
rpg_statements.zig are unchanged. A further lane needs a public probe whose
main procedure the compiler wraps with a prologue or epilogue statement
between the numbered markers and the body, captured first.

Gates

{"checks":{"net_statements":0},"census":{"statuses":{"recovered":645,"partial":0,"unresolved":0},"regressions":0,"newly_recovered":0},"golden":"golden floor 173 ceiling 0 <= dump 173/5/0","legend":"current","emit":{"worse":[],"better":0,"newly_clean":0,"clean_delta":0,"base":738,"new":738},"twins":{"groups":1022,"recovered":1015,"regressions":[],"newly":0},"allgroups":{"regressions":[],"newly":[],"worse":[]},"unit":{"exit":0,"last":"ship-unit: no test file changed"},"full_check":{"exit":0,"seconds":1896}}
# rpg_shape.compilerOrigin: lane Co finds no public layout for the statement_marker refusal; nothing changes Negative result. No source, test or emit byte changes in this pull request. Question: which public procedure layouts reach `compilerOrigin` s01 (`statement_marker`, the procedure does not open with statement 2100000001 and close with 2100000002), while carrying a compiler-originated marker that the shape marker, entry procedure and INIT call tests would accept? Measured on a Debug build of the branch base (fba2d222), `SOURCERER_TRACE_REFUSALS=1`, over every public `archive.savf` under `src/testdata/savf` except LEMONADE (no private, held-out or exam material): - Every procedure that carries 2100000001 or 2100000002 (23 archives: ACCESS, DSPLY, MONITOR, TSTRIP, TSTRIP-STRIPPED and the EXPERIMENTS probes format-base, format-rename, gotos-static, shared-io-full, shared-io-none and others) lists 2100000001 first and 2100000002 last among its numbered statements. The groups outside the pair are `statement none` (the unnumbered instructions before the first and after the last numbered statement), not numbered statements in between. No procedure has either marker at another position, and none has only one of the pair. - No archive with a marker procedure appears among the archives that fire s01. The refusal never reaches a layout that has the marker. - The archives that fire s01 (FLOW, OPS, INIT and others) carry no 2100000001 or 2100000002 at all: their main procedure starts at the source-statement marker 1000001 and ends at 1000002 (`OPTION(*SRCSTMT)`). That is a different marker pair, not a displaced one. Accepting it would accept a marker by number alone, which the brief rules out, and those statements are read as source, not as compiler origin. So the placement test has no public case to widen to, and a red test cannot be written on a public probe. `compilerOrigin`, `compilerProved` and `rpg_statements.zig` are unchanged. A further lane needs a public probe whose main procedure the compiler wraps with a prologue or epilogue statement between the numbered markers and the body, captured first. ## Gates ``` {"checks":{"net_statements":0},"census":{"statuses":{"recovered":645,"partial":0,"unresolved":0},"regressions":0,"newly_recovered":0},"golden":"golden floor 173 ceiling 0 <= dump 173/5/0","legend":"current","emit":{"worse":[],"better":0,"newly_clean":0,"clean_delta":0,"base":738,"new":738},"twins":{"groups":1022,"recovered":1015,"regressions":[],"newly":0},"allgroups":{"regressions":[],"newly":[],"worse":[]},"unit":{"exit":0,"last":"ship-unit: no test file changed"},"full_check":{"exit":0,"seconds":1896}} ```
docs/changes: lane Co finds no public layout for the compilerOrigin placement refusal
All checks were successful
binjovi/ci Binjovi completed the frozen plan
c4b6bc7c69
binjovi-bot manually merged commit c4b6bc7c69 into trunk 2026-11-17 05:50:23 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
sean/sourcerer!811
No description provided.