Call to fn with target_feature that's enabled program-wide cites a very generic error code

Code

// https://rust.godbolt.org/z/evxnYch3z

// When building for x86_64:

pub fn movemask(a: core::arch::x86_64::__m128i) -> i32 {
    core::arch::x86_64::_mm_movemask_epi8(a)
}

Current output

error[E0133]: call to function `_mm_movemask_epi8` with `#[target_feature]` is unsafe and requires unsafe block
 --> <source>:3:5
  |
3 |     core::arch::x86_64::_mm_movemask_epi8(a)
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to function with `#[target_feature]`
  |
  = help: in order for the call to be safe, the context requires the following additional target feature: sse2
  = note: the sse2 target feature being enabled in the build configuration does not remove the requirement to list it in `#[target_feature]`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0133`.

Desired output

A different error number that would provide a design justification for why a target feature being enable in the build configuration does not remove the requirement to list it in `#[target_feature]`.

Rationale and extra context

E0133 is a very generic "Unsafe code was used outside of an unsafe block." explanation.

Considering how disappointing it is that even after Rust 1.87, unsafe can't be elided for architecture-specific intrinsics that are available in the target (notably sse2 when targeting x86 or x86_64 and neon when targeting aarch64), expected a different error number that would provide a design justification for why a target feature being enable in the build configuration does not remove the requirement to list it in #[target_feature].

Other cases

Rust Version

rustc 1.98.0-nightly (91fe22da8 2026-06-21)

(Don't know how to get something more precise from Compiler Explorer.)

Anything else?

No response

Start by reproducing the x86_64 example and reading the existing E0133 diagnostic, including its target_feature help and note. Trace how this call is classified and how the diagnostic is selected; done means the case receives a distinct error code or explanation that justifies requiring #[target_feature] even when the feature is enabled in the build configuration.