Rollup of 4 pull requests

[m-ou-se]

Successful merges:

• rustdoc doctest: include signal number in exit status #95783 (rustdoc doctest: include signal number in exit status)
• parse_tt: a few more tweaks #95794 (parse_tt: a few more tweaks)
• [bootstrap] Grab the right FileCheck binary for dist when cross-compiling. #95963 ([bootstrap] Grab the right FileCheck binary for dist when cross-compiling.)
• Don't test -Cdefault-linker-libraries=yes when cross compiling. #95975 (Don't test -Cdefault-linker-libraries=yes when cross compiling.)

Failed merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

[m-ou-se]

@bors r+ rollup=never p=4

[bors]

📌 Commit 550a510 has been approved by m-ou-se

[bors]

⌛ Testing commit 550a510 with merge 52ca603...

[bors]

☀️ Test successful - checks-actions
Approved by: m-ou-se
Pushing 52ca603 to master...

[rust-timer]

Finished benchmarking commit (52ca603): comparison url.

Summary:

• Primary benchmarks: no relevant changes found
• Secondary benchmarks: mixed results

	Regressions 😿 (primary)	Regressions 😿 (secondary)	Improvements 🎉 (primary)	Improvements 🎉 (secondary)	All 😿 🎉 (primary)
count1	0	13	0	7	0
mean2	N/A	1.7%	N/A	-0.4%	N/A
max	N/A	3.0%	N/A	-0.6%	N/A

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. number of relevant changes ↩

2. the arithmetic mean of the percent change ↩

[pnkfelix]

Visiting for weekly performance triage.

• the big hit here was to tt-muncher (a secondary benchmark), which regressed on 10 different configurations, by amounts varying from 1.4% up to 3.0%.
• the cachegrind diff for the 3.0% hit is here: https://gist.github.com/7674ad03c8f72705eb5bd2651202f40a
• that cachegrind diff leads pnkfelix to think that PR parse_tt: a few more tweaks #95794: "parse_tt: a few more tweaks" is the cause of the regression, specifically commit 4ba6096
• however, that PR went through multiple rounds of performance evaluation.
• in any case, looking at the graph for tt-muncher indicates that whatever performance hit was suffered, it was subsequently resolved by PR Remove <mbe::TokenTree as Clone> #95928.

@rustbot label: +perf-regression-triaged