Implement -Clink-self-contained=-linker opt out

[lqd]

This implements the -Clink-self-contained opt out necessary to switch to lld by changing rustc's defaults instead of cargo's.

Components that are enabled and disabled on the CLI are recorded, for the purpose of being merged with the ones which the target spec will declare (I'll open another PR for that tomorrow, for easier review).

For MCP510, we now check whether using the self-contained linker is disabled on the CLI. Right now it would only be sensible to with -Zgcc-ld=lld (and I'll add some checks that we don't both enable and disable a component on the CLI in a future PR), but the goal is to simplify adding the check of the target's enabled components here in the follow-up PRs.

r? @petrochenkov

[rustbot]

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.

These commits modify compiler targets.
(See the Target Tier Policy.)

[lqd]

I've pulled in the commits related to checking -Clink-self-contained consistency from #116035.

@rustbot ready

[lqd]

Rebased to fix conflicts.

-Zgcc-ld=lld was the only way to enable the self-contained linker without using the -Clink-self-contained flag, and since it was removed in #116514 there's no opt out this PR can offer per se, only the structures and functions needed to implement it.

So, checking if the linker component is explicitly disabled on the CLI, will have to be done when the target specs can also enable it, in #116035.

[lqd]

Rebased to fix conflicts.

[petrochenkov]

@bors r+

[bors]

📌 Commit d634cc5 has been approved by petrochenkov

It is now in the queue for this repository.

[bors]

⌛ Testing commit d634cc5 with merge d756371...

[rust-log-analyzer]

The job aarch64-gnu failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

test [ui] tests/ui/drop/issue-2735.rs ... ok
test [ui] tests/ui/drop/issue-35546.rs ... ok
test [ui] tests/ui/drop/issue-48962.rs ... ok
test [ui] tests/ui/drop/issue-979.rs ... ok
##[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test [ui] tests/ui/drop/no-drop-flag-size.rs ... ok
test [ui] tests/ui/drop/issue-90752.rs ... ok
test [ui] tests/ui/drop/nondrop-cycle.rs ... ok


test [ui] tests/ui/drop/issue-90752-raw-ptr-shenanigans.rs ... ok
##[group]Clock drift check
  local time: test [ui] tests/ui/drop/issue-23338-ensure-param-drop-order.rs ... ok
test [ui] tests/ui/drop/issue-30018-nopanic.rs ... ok
Session terminated, killing shell... ...killed.
##[error]The operation was canceled.

[bors]

💔 Test failed - checks-actions

[lqd]

Session terminated, killing shell... ...killed.
Error: The operation was canceled.

@bors retry

[bors]

⌛ Testing commit d634cc5 with merge 5aa23be...

[bors]

☀️ Test successful - checks-actions
Approved by: petrochenkov
Pushing 5aa23be to master...

[rust-timer]

Finished benchmarking commit (5aa23be): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

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

Max RSS (memory usage)

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

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

Cycles

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

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

Binary size

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

Bootstrap: 627.902s -> 627.767s (-0.02%)
Artifact size: 271.29 MiB -> 271.31 MiB (0.00%)