feat: validate declaration headers before MIR lowering - #692
Merged
Conversation
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
main, local-header, summary, and structural drop-set metadata before MIR publication;FnEffectthrough checked HIR and strip it into an explicit six-field MIR imported record;FnOrigin, preserving existing per-unit exportability and ABI behavior;mir-header-validationbenchmark row.Verification
cargo build --workspace --lockedscripts/test-pr.shcargo clippy --workspace --all-targets --locked -- -D warningscargo check -p align_mir --tests --lockedbench/library_boundaryprovenance run with the LLVM 22 toolchainThe pre-PR gate was recorded by
scripts/pre-pr.shagainst the final HEAD. On this macOS host,DYLD_SHARED_REGION=privatestalls test-binary startup in_dyld_start; the successful gate usedthe explicit LLVM 22 paths without that variable.