Rollup of 10 pull requests

[matthiaskrgr]

Successful merges:

• Normalize consts' tys when relating with adt_const_params #97709 (Normalize consts' tys when relating with adt_const_params)
• Remove the infer_static_outlives_requirements feature #97875 (Remove the infer_static_outlives_requirements feature)
• interpret: unify offset_from check with offset check #97960 (interpret: unify offset_from check with offset check)
• Make type_changing_struct_update no longer an incomplete feature #97999 (Make type_changing_struct_update no longer an incomplete feature)
• Remove unnecessary to_string and String::new #98043 (Remove unnecessary to_string and String::new)
• [issues:97981] del unrelated comment #98044 ([issues:97981] del unrelated comment)
• Document an edge case of str::split_once #98049 (Document an edge case of str::split_once)
• Add some more regression tests for #67945 #98050 (Add some more regression tests for ICE: index out of bounds: the len is 0 but the index is 0 #67945)
• Fix error message for download-ci-llvm #98054 (Fix error message for download-ci-llvm)
• Update miri #98057 (Update miri)

Failed merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

[matthiaskrgr]

@bors r+ rollup=never p=10

[bors]

📌 Commit af1f614 has been approved by matthiaskrgr

[bors]

⌛ Testing commit af1f614 with merge ca122c7...

[bors]

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing ca122c7 to master...

[rust-highfive]

📣 Toolstate changed by #98066!

Tested on commit ca122c7.
Direct link to PR: #98066

🎉 miri on windows: build-fail → test-pass (cc @oli-obk @RalfJung @eddyb).
🎉 miri on linux: build-fail → test-pass (cc @oli-obk @RalfJung @eddyb).

[rust-timer]

Finished benchmarking commit (ca122c7): comparison url.

Instruction count

• Primary benchmarks: 😿 relevant regressions found
• Secondary benchmarks: mixed results

	mean1	max	count2
Regressions 😿 (primary)	0.5%	0.6%	4
Regressions 😿 (secondary)	0.4%	0.5%	11
Improvements 🎉 (primary)	N/A	N/A	0
Improvements 🎉 (secondary)	-0.3%	-0.3%	4
All 😿🎉 (primary)	0.5%	0.6%	4

Max RSS (memory usage)

Results

• Primary benchmarks: 😿 relevant regression found
• Secondary benchmarks: 😿 relevant regression found

	mean1	max	count2
Regressions 😿 (primary)	2.2%	2.2%	1
Regressions 😿 (secondary)	4.7%	4.7%	1
Improvements 🎉 (primary)	N/A	N/A	0
Improvements 🎉 (secondary)	N/A	N/A	0
All 😿🎉 (primary)	2.2%	2.2%	1

Cycles

Results

• Primary benchmarks: 🎉 relevant improvement found
• Secondary benchmarks: no relevant changes found

	mean1	max	count2
Regressions 😿 (primary)	N/A	N/A	0
Regressions 😿 (secondary)	N/A	N/A	0
Improvements 🎉 (primary)	-2.3%	-2.3%	1
Improvements 🎉 (secondary)	N/A	N/A	0
All 😿🎉 (primary)	-2.3%	-2.3%	1

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please open an issue or create a new PR that fixes the regressions, add a comment linking to the newly created issue or PR, and then add the perf-regression-triaged label to this PR.

@rustbot label: +perf-regression

Footnotes

1. the arithmetic mean of the percent change ↩ ↩² ↩³

2. number of relevant changes ↩ ↩² ↩³

[pnkfelix]

• diesel-1.4.8 regressed by 0.5% for variations on check/debug/opt and incr-full/full. That's the only primary regression, and its within the noise level that we're currently associating with diesel, I think.
• The other regressions are wf-projection-stress-65510, projection-caching, regression-31157, and wg-grammar.
• wf-projection-stress-65510 and regression-31157 are canaries where we are trying to catch a massive regression, not a minor one like the ones presented here.
• given that this is a rollup and the remaining regressions are well under 0.5%, I think that's the limit to the amount of investigation I want to do here.

@rustbot label: +perf-regression-triaged