Miri subtree update

[RalfJung]

r? @ghost

[rustbot]

The Miri subtree was changed

cc @rust-lang/miri

These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged. Otherwise, you can ignore this comment.

[RalfJung]

@bors r+

[bors]

:pushpin: Commit 88e3e682869d6c6f28c86cd2ee38a2164dbcd8d0 has been approved by RalfJung

It is now in the queue for this repository.

[workingjubilee]

@bors p=1

[bors]

:hourglass: Testing commit 88e3e682869d6c6f28c86cd2ee38a2164dbcd8d0 with merge 1677d46cb128cc8f285dbd32b0dc4d7a46437050...

[bors]

:sunny: Test successful - checks-actions Approved by: RalfJung Pushing 1677d46cb128cc8f285dbd32b0dc4d7a46437050 to master...

[github-actions[bot]]

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 8ce228758651aa58c4d34e3bd65bf70a251da27e (parent) -> 1677d46cb128cc8f285dbd32b0dc4d7a46437050 (this PR)

Test differences

No test diffs found

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 1677d46cb128cc8f285dbd32b0dc4d7a46437050 --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. mingw-check-tidy: 92.9s -> 66.1s (-28.9%)
2. dist-aarch64-apple: 6852.3s -> 5385.4s (-21.4%)
3. dist-apple-various: 8234.7s -> 7066.4s (-14.2%)
4. x86_64-apple-1: 8007.2s -> 6977.5s (-12.9%)
5. dist-ohos-aarch64: 4623.4s -> 4212.4s (-8.9%)
6. x86_64-apple-2: 4825.2s -> 4407.8s (-8.7%)
7. dist-ohos-x86_64: 4498.4s -> 4123.3s (-8.3%)
8. dist-powerpc64le-linux-musl: 5457.3s -> 5024.1s (-7.9%)
9. dist-x86_64-apple: 9394.8s -> 10067.5s (7.2%)
10. dist-powerpc64-linux: 5359.1s -> 5006.7s (-6.6%)

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.

[rust-timer]

Finished benchmarking commit (1677d46cb128cc8f285dbd32b0dc4d7a46437050): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.4%	[-0.4%, -0.4%]	2
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary -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)	-2.1%	[-2.1%, -2.1%]	1
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-2.1%	[-2.1%, -2.1%]	1

Cycles

Results (secondary -1.4%)

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)	-1.4%	[-1.4%, -1.4%]	1
All ❌✅ (primary)	-	-	0

Binary size

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

Bootstrap: 755.415s -> 755.082s (-0.04%) Artifact size: 372.14 MiB -> 372.15 MiB (0.00%)