-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Rollup of 10 pull requests #141605
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
Rollup of 10 pull requests #141605
Conversation
Signed-off-by: onur-ozkan <work@onurozkan.dev>
Signed-off-by: onur-ozkan <work@onurozkan.dev>
minor improvements on running miri It should be clear from the commit messages when reviewing them one by one.
…lcnr Avoid obligation construction dance with query region constraints And some renaming...
Emit dummy open drop for unsafe binder Fixes rust-lang#141394 We can't taint the body in wfcheck when we have a `T: Copy` bound failure, so we end up binding MIR here. Emit a dummy open drop so that drop elaboration doesn't fail. r? oli-obk
…ures, r=oli-obk Properly analyze captures from unsafe binders We need to represent the unsafe binder unwrap as an adjustment in HIR. Pretty straightforward b/c we already represent it as a projection elem in MIR. Fixes rust-lang#141418 Fixes rust-lang#141417 r? oli-obk
…rce, r=oli-obk Deduplicate dyn compatibility violations due to coercion Don't unnecessarily emit dyn compatibility violations due to coercion to a non-dyn-compatible target type. For us to even have that target type, we would have had to write `dyn Trait` somewhere in source, and that would have led to us *already* emitting a dyn compatibility violation when checking that user written type is WF. r? oli-obk
…k, r=oli-obk further deduplicate ast visitor code Previous PR: rust-lang#141249 Tracking issue: rust-lang#127615 r? `@oli-obk`
interpret: add allocation parameters to `AllocBytes` Necessary for a better implementation of [rust-lang/miri#4343](rust-lang/miri#4343). Also included here is the code from that PR, adapted to this new interface for the sake of example and so that CI can run on them; the Miri changes can be reverted and merged separately, though. r? `@RalfJung`
speed up charsearcher for ascii chars attempt at fixing rust-lang#82471 this implementation should be valid because ascii characters are always one byte and there are no continuation bytes that overlap with ascii characters im not completely sure that this is _always_ an improvement but it seems to be an improvement for this case and i dont think it can significantly regress any cases
add a dedicated section for compiler environment variables in the unstable book rendered:  fixes rust-lang#141523
…ukang Fix `unused_braces` lint suggestion when encountering attributes This PR fixes the `unused_braces` lint suggestion when encountering attributes by not removing them in the suggestion. Fixes rust-lang#141549
@bors r+ rollup=never p=5 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 40d2563ea2 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 40d2563 (parent) -> 2805e1d (this PR) Test differencesShow 68 test diffsStage 1
Stage 2
Additionally, 62 doctest diffs were found. These are ignored, as they are noisy. Job group index
Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 2805e1dc4c18ed4c84d161502c48da870c56f68a --output-dir test-dashboard And then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
Finished benchmarking commit (2805e1d): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowOur benchmarks found a performance regression caused by this PR. Next Steps:
@rustbot label: +perf-regression Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary -1.9%, secondary -3.3%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResults (primary 2.2%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeResults (primary -0.0%, secondary -0.2%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Bootstrap: 778.13s -> 778.675s (0.07%) |
Started a bunch of perf. runs. |
Yeah pretty weird. Unsafe binders shouldn't be applicable to doc benchmarks, I presume. We'll see what happens. It'd probably be faster to check |
Crap, the unrolled builds are broken due to the recent rust-lang-ci migration. Will try to fix. |
Restarted all the failed try builds. Once they finish, we should be able to restart the perf. runs. |
Hmm, looks like it won't be that easy, the builds are somehow cached and they still fail :/ I'll try to revert & perf. test some of the PRs. |
Successful merges:
AllocBytes
#141513 (interpret: add allocation parameters toAllocBytes
)unused_braces
lint suggestion when encountering attributes #141550 (Fixunused_braces
lint suggestion when encountering attributes)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup