Repository navigation
More properties on the same corpus; finding 8 reduced and confirmed - #20
Merged
Merged
Conversation
…-opt-level=3 The difference needs MIR inlining from core; a generic local helper, a non-generic function or level 2 do not show it. All the level-4 fuzz differences go away with -Zinline-mir=no. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018Mnrg9JXj9X1ht6Qkz2ybh
…ver, threads Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018Mnrg9JXj9X1ht6Qkz2ybh
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018Mnrg9JXj9X1ht6Qkz2ybh
… test results docs/hunt/upstream-alloc-reference.patch makes the incremental cache refer to allocations decoded from another crate's metadata instead of copying them; both reproductions then build the same incrementally as clean. One fuzzer case remains. The tests of the ten crates give the same results under -Znext-solver=globally as under the old solver. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018Mnrg9JXj9X1ht6Qkz2ybh
…its limits Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018Mnrg9JXj9X1ht6Qkz2ybh
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018Mnrg9JXj9X1ht6Qkz2ybh
…ches kept locally Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018Mnrg9JXj9X1ht6Qkz2ybh
…age attributes, mixed_site hygiene, inlining across crates Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018Mnrg9JXj9X1ht6Qkz2ybh
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018Mnrg9JXj9X1ht6Qkz2ybh
zmaril
marked this pull request as draft
October 8, 2026 16:36
zmaril
marked this pull request as ready for review
October 9, 2026 11:32
zmaril
added this pull request to stack #23
October 9, 2026 14:15
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.
Follows the merged stack.
docs/hunt/threads-def-order-stopgap.patch, testing only): definitions that queries create are made on one thread, in order, before rustc'scommit_end_of_determinism. Threaded fuzzing on the unmodifiedfixtures/sinkis now clean (644+ rebuilds).docs/props.md), on sink and the ten replayed crates:-Zmir-opt-level=0..4×-Copt-level=0/3: 110 builds, no failures.-Copt-level=0vs3: 2,239 tests, none differ; sink's 60 runtime checks identical.-Zmir-opt-level=3, an incremental rebuild encodes an allocation from MIR inlined fromcoretwice. Found by fuzzing at-Zmir-opt-level=4, named by the reuse check (whose sharing reports now print the allocation), reduced to one line (pub fn f<T>(v: &[T]) -> Option<&[T]> { v.get(..3) }), on 1.60.0 through the nightly. An experimental cache change (docs/hunt/upstream-alloc-reference.patch) that refers to upstream allocations instead of copying them confirms the mechanism; one fuzzer case has another source.rustc/regen-patches.shregenerates the patch files and checks the stack reproduces the compiler tree;fuzz-replay.pykeeps the last builds' output.🤖 Generated with Claude Code
https://claude.ai/code/session_018Mnrg9JXj9X1ht6Qkz2ybh