Always statically link std into rustc_driver

[Zoxc]

This always statically links std into rustc_driver by removing the MinGW exception.

try-job: dist-x86_64-mingw

[Zoxc]

@bors try

[rust-bors]

☀️ Try build successful (CI)
Build commit: 70a8565 (70a85652f1b6645ac932059b7520b7a7f2de3bca)
Base parent: b070f45 (b070f45ad92ed45b20e57d9483a21657d0d00715)

[rustbot]

r? @clubby789

rustbot has assigned @clubby789.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

• Owners of files modified in this PR: bootstrap
• bootstrap expanded to 6 candidates
• Random selection from Mark-Simulacrum, clubby789

[rustbot]

This PR was rebased onto a different main 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.

[Zoxc]

cc @Kobzol Another bootstrap cleanup

[Kobzol]

Thanks, left one nit.

r? kobzol

View changes since this review

[Kobzol]

This comment should be updated.

[Kobzol]

@bors try @rust-timer queue

View changes since this review

[Kobzol]

@bors try jobs=dist-x86_64-linux-quick

[rust-bors]

☀️ Try build successful (CI)
Build commit: 268c2a8 (268c2a844322d1450c24e14a2707bd363c7cbd66)
Base parent: 88f7399 (88f7399cb4912680976e1c342ea7661b9dc84940)

[Kobzol]

@rust-timer build 268c2a8

[rust-timer]

Finished benchmarking commit (268c2a8): comparison URL.

Overall result: ❌✅ regressions and improvements - please read:

Benchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf.

Next, please: If you can, justify the regressions found in this try perf run in writing along with @rustbot label: +perf-regression-triaged. If not, fix the regressions and do another perf run. Neutral or positive results will clear the label automatically.

@bors rollup=never rustc-perf
@rustbot label: -S-waiting-on-perf +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.6%	[0.6%, 0.6%]	3
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.4%	[-0.5%, -0.2%]	6
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary 0.4%, secondary 0.0%)

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

	mean	range	count
Regressions ❌ (primary)	6.8%	[6.8%, 6.8%]	1
Regressions ❌ (secondary)	4.7%	[3.1%, 6.2%]	2
Improvements ✅ (primary)	-6.0%	[-6.0%, -6.0%]	1
Improvements ✅ (secondary)	-1.1%	[-4.2%, -0.4%]	8
All ❌✅ (primary)	0.4%	[-6.0%, 6.8%]	2

Cycles

Results (secondary -0.5%)

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)	1.6%	[0.5%, 2.8%]	4
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-1.2%	[-3.1%, -0.4%]	14
All ❌✅ (primary)	-	-	0

Binary size

Results (secondary -0.0%)

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

Bootstrap: 460.09s -> 459.457s (-0.14%)
Artifact size: 398.62 MiB -> 398.66 MiB (0.01%)