Refactor remove_noop_landing_pads in two loops.#147099
Refactor remove_noop_landing_pads in two loops.#147099bors merged 3 commits intorust-lang:masterfrom
Conversation
35adce2 to
9bb173f
Compare
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Refactor remove_noop_landing_pads in two loops.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (5213325): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary -1.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 2.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 469.268s -> 471.818s (0.54%) |
|
Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt |
|
r? compiler |
|
|
||
| // This is a post-order traversal, so that if A post-dominates B | ||
| // then A will be visited before B. | ||
| for &bb in body.basic_blocks.reverse_postorder().iter().rev() { |
There was a problem hiding this comment.
why body.basic_blocks.reverse_postorder().iter().rev() instead** of traversal::postorder(body)?
r=me otherwise
There was a problem hiding this comment.
94b2c30 uses traversal::postorder, which simplifies some things too.
9bb173f to
94b2c30
Compare
|
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
@bors r+ |
|
☀️ Test successful - checks-actions |
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 ff5be13 (parent) -> d773bd0 (this PR) Test differencesNo test diffs found Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard d773bd07d63a74adcf25ea5f4aae986be94cac5e --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 (d773bd0): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary -0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -2.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 473.87s -> 473.455s (-0.09%) |
The point is to avoid clearing the CFG cache as often.
r? @ghost for perf