Leave from CopyProp early when there are no replacements

[tmiasko]

r? cjgillot

[rustbot]

Some changes occurred to MIR optimizations

cc @rust-lang/wg-mir-opt

[cjgillot]

@bors try @rust-timer queue

[bors]

⌛ Trying commit c353539 with merge fb8fc2c...

[bors]

☀️ Try build successful - checks-actions
Build commit: fb8fc2c (fb8fc2c158d909df693abe433f3aa7da3b68db9e)

[rust-timer]

Finished benchmarking commit (fb8fc2c): comparison URL.

Overall result: no relevant changes - no action needed

Benchmarking 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
@rustbot label: -S-waiting-on-perf -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results (secondary -2.1%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-2.1%	[-3.2%, -1.6%]	3
All ❌✅ (primary)	-	-	0

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 689.082s -> 689.371s (0.04%)
Artifact size: 371.89 MiB -> 371.87 MiB (-0.01%)

[cjgillot]

@bors r+

[bors]

📌 Commit c353539 has been approved by cjgillot

It is now in the queue for this repository.

[workingjubilee]

forcing rollup=never drain:

@bors p=5

[bors]

⌛ Testing commit c353539 with merge 8cf5fad...

[bors]

☀️ Test successful - checks-actions
Approved by: cjgillot
Pushing 8cf5fad to master...

[github-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 2801f9a (parent) -> 8cf5fad (this PR)

Test differences

No test diffs found

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 8cf5fad73d4e8f41863ecc3bcfa114eabc951faa --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

1. dist-apple-various: 7019.9s -> 8577.7s (22.2%)
2. x86_64-apple-2: 5407.0s -> 4321.1s (-20.1%)
3. mingw-check-1: 1890.1s -> 1576.1s (-16.6%)
4. dist-x86_64-msvc-alt: 9868.4s -> 8431.0s (-14.6%)
5. i686-gnu-2: 6496.5s -> 5569.9s (-14.3%)
6. i686-gnu-1: 8181.8s -> 7327.1s (-10.4%)
7. x86_64-gnu-tools: 3731.6s -> 3343.3s (-10.4%)
8. x86_64-gnu-llvm-19-1: 3676.4s -> 3317.2s (-9.8%)
9. x86_64-rust-for-linux: 2959.9s -> 2673.8s (-9.7%)
10. x86_64-apple-1: 7431.8s -> 6787.1s (-8.7%)

How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.