Repository navigation
[AUTOMATED] Export conservative SSA definition line provenance - #203
Merged
Merged
Conversation
This was referenced Oct 14, 2026
sjkim1127
marked this pull request as ready for review
October 19, 2026 10:03
sjkim1127
enabled auto-merge
October 19, 2026 10:04
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
1 participant
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.
[AUTOMATED]
Change
Transport conservative scalar-SSA assignment-result origins to physical NIR/HIR
output lines and additive CLI JSON. Preserve defined binding ownership so an
adapter never assigns LHS definition PCs to RHS variables.
Reject input/phi/cloned/ambiguous/repeated definitions and unproved lines. Track
each layer independently; header/warning line deletion remaps or abstains.
No IR, effects, code formatting, type inference or semantic repair is introduced.
Evidence
Dataset: C++ qualification corpus,
frozen revision used in validation.
Clean main 52c81dd baseline and final release candidate independently generated
250/250 stripped qualification functions. NIR and direct variable lists are
identical across all 250. 105 functions carry 237 scoped NIR line maps; all PCs
passed native instruction validation. Final-binary repeated Linux/Windows/macOS
probes were deterministic. The source/ABI DecBench proposal uses these mappings.
1,328 pcode/CLI nextest tests passed, 1 skipped; relevant checks, release build,
workspace fmt and owner-boundary scan passed. See the proposal and CLI contract.
This is mechanical provenance transport. No execution parity, semantic/readability
improvement, full expression lineage or official ranking is claimed.