Don't try to remove drop_in_place calls in RemoveUnneededDrops#155044
Don't try to remove drop_in_place calls in RemoveUnneededDrops#155044rust-bors[bot] merged 1 commit intorust-lang:mainfrom
drop_in_place calls in RemoveUnneededDrops#155044Conversation
|
Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt |
| unsafe fn slice_in_place(ptr: *mut [char]) { | ||
| // CHECK-LABEL: fn slice_in_place(_1: *mut [char]) | ||
| // CHECK: bb0: { | ||
| // CHECK-NEXT: return; | ||
| // CHECK: bb0: { | ||
| // CHECK-NEXT: StorageLive(_2); | ||
| // CHECK-NEXT: _2 = copy _1; | ||
| // CHECK-NEXT: StorageDead(_2); | ||
| // CHECK-NEXT: return; | ||
| // CHECK-NEXT: } | ||
| std::ptr::drop_in_place(ptr) | ||
| } |
There was a problem hiding this comment.
idk how this used to pass, given that the diff is unchanged...
There was a problem hiding this comment.
You removed the compile-flags, so that probably impacted it? The filecheck validations are on final mir always...
2a174db to
fa73f03
Compare
|
@bors try @rust-timer queue Just in case :) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Don't try to remove `drop_in_place` calls in `RemoveUnneededDrops`
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (7c3a7ce): comparison URL. Overall result: no relevant changes - no action neededBenchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf. @bors rollup=never Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (secondary -1.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 9.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 488.4s -> 489.587s (0.24%) |
|
@bors rollup=maybe |
|
My suggestion was addressed and CI is clean |
This comment has been minimized.
This comment has been minimized.
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 d1d3ef4 (parent) -> c7c14d4 (this PR) Test differencesShow 7 test diffsStage 1
Stage 2
Additionally, 2 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 c7c14d4fb0310429e05e1a24dcf879053ee25b09 --output-dir test-dashboardAnd 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 (c7c14d4): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (secondary 6.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 0.8%, secondary -2.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 491.73s -> 490.09s (-0.33%) |
As per my justification in #154327 (comment)
r? scottmcm