Remove unused features

[mu001999]

Detected by #152164.

Only allow unused_features if there are complex platform-specific features enabled.

[rustbot]

Some changes occurred in exhaustiveness checking

cc @Nadrieril

Some changes occurred in compiler/rustc_codegen_cranelift

cc @bjorn3

rust-analyzer is developed in its own repository. If possible, consider making this change to rust-lang/rust-analyzer instead.

cc @rust-lang/rust-analyzer

The Miri subtree was changed

cc @rust-lang/miri

[rustbot]

r? @jdonszelmann

rustbot has assigned @jdonszelmann.
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: compiler
• compiler expanded to 67 candidates
• Random selection from 14 candidates

[Nadrieril]

Hi, thanks for your contribution!

We should not remove these feature gates from tests. Features in tests sometimes test very subtle interactions and we don't want to break that. Also for tools and rustdoc we generally don't touch these directories unless strictly necessary; we're not running their whole test suite in CI so we could be removing a feature they actually use.

I'm also of the opinion that replacing a feature with cfg_attr(..., feature(...)) is noise and not worth the precision. E.g. all the platform-specific stuff in core.

The rest looks good to me, that's some nice cleanups.

[mu001999]

@Nadrieril Make sense, I will keep the removal in compiler and replace the rest with just allowing unused_features

[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.