`armv7a-none-eabi` sets both fpregs and soft-float features

I tried this code:

rustc +nightly --print cfg --target armv7a-none-eabi | grep target_feature

I expected to see this happen: no FPU related features would be set

Instead, this happened: both soft-float and vfp3 features were set

target_feature="aclass"
target_feature="d32"
target_feature="dsp"
target_feature="fp64"
target_feature="fpregs"
target_feature="soft-float"
target_feature="thumb2"
target_feature="v5te"
target_feature="v6"
target_feature="v6k"
target_feature="v6m"
target_feature="v6t2"
target_feature="v7"
target_feature="v8m"
target_feature="vfp2"
target_feature="vfp2sp"
target_feature="vfp3"

This doesn't happen on targets like armv7r-none-eabi.

rustc +nightly --print cfg --target armv7r-none-eabi | grep target_feature

target_feature="dsp"
target_feature="rclass"
target_feature="thumb2"
target_feature="v5te"
target_feature="v6"
target_feature="v6k"
target_feature="v6m"
target_feature="v6t2"
target_feature="v7"
target_feature="v8m"

Meta

rustc --version --verbose:

rustc +nightly --version --verbose
rustc 1.100.0-nightly (cea272fa3 2026-09-07)
binary: rustc
commit-hash: cea272fa356e94bd2ee2cadf376630aa0683867a
commit-date: 2026-09-07
host: aarch64-apple-darwin
release: 1.100.0-nightly
LLVM version: 23.1.1

Reproduce the issue with rustc +nightly --print cfg --target armv7a-none-eabi and compare its target_feature output with armv7r-none-eabi. Trace how these target configurations determine the reported features. Done means armv7a-none-eabi no longer reports contradictory soft-float and FPU-related features.