-
-
Notifications
You must be signed in to change notification settings - Fork 150
fix(codegen): sort closure-source emission so the same input compiles to the same IR (#7038) #7039
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+30
−4
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| Fixed non-deterministic LLVM IR: `emit_artifacts` iterated `hir.closure_source_text` | ||
| (a `HashMap`) when emitting retained closure-source constants, so the `@.str.N` | ||
| numbering of those constants was a per-process permutation — the same input | ||
| compiled to different IR on every run. | ||
|
|
||
| This was not cosmetic. It silently invalidates any A/B comparison of raw LLVM IR, | ||
| a technique several representation-selection and GC investigations relied on for | ||
| evidence. PR #7037 hit it directly: its first proof that `--opt-report` was | ||
| observational passed on nondeterministic output and had to be redone with four | ||
| runs per arm and a normalizer. | ||
|
|
||
| Measured over 6 compiles of one file (md5 of the concatenated per-module `.ll`): | ||
| 5 distinct hashes before, 1 after. Emission order is the only thing that changes. | ||
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Use probabilistic wording for the nondeterminism claim.
HashMapiteration can vary across processes, but independent runs may still produce the same order. Replace “different IR on every run” with “can produce different IR across runs.”🤖 Prompt for AI Agents