Stabilize the avx512 target features

[sayantn]

This PR stabilizes the AVX512 target features - see this comment.

Tracking Issue - #44839

DO NOT MERGE now, because the runtime detection for 5 features are guarded on avx512_target_feature, so rust-lang/stdarch#1757 has a temporary fix which changes the feature name of these. We need to FCP these together with all the AVX512 target features, after that and merge of rust-lang/stdarch#1760, we can again do a stdarch update and merge this.

The target feature UI tests have been changed to cmpxchg16b (arbitrarily chosen, please comment if some other feature will be better)

Updates stdarch

Needs to wait for bootstrap bump due to s390x target features not being available in bootstrap (#139279)

[rustbot]

r? @davidtwco

rustbot has assigned @davidtwco.
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

[rustbot]

⚠️ Warning ⚠️

• These commits modify submodules.

[rustbot]

The Miri subtree was changed

cc @rust-lang/miri

[Amanieu]

Nominating for T-lang FCP. This stabilizes the AVX512 target features which is a per-requisite for stabilizing the AVX-512 intrinsics tracked in #111137.

[ehuss]

Can you also send a PR to update https://github.com/rust-lang/reference/blob/master/src/attributes/codegen.md#x86-or-x86_64?

[rust-log-analyzer]

The job mingw-check failed! Check out the build log: (web) (plain)

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

[RUSTC-TIMING] build_script_build test:false 0.505
error: unexpected `cfg` condition value: `vector-enhancements-2`
   --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:802:19
    |
802 |         all(test, target_feature = "vector-enhancements-2"),
    |                   ^^^^^^^^^^^^^^^^^-----------------------
    |                                    |
    |                                    help: there is a expected value with a similar name: `"vector-enhancements-1"`
    |
    = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-int8`, `amx-tile`, `atomics`, `avx`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, `avx512f`, `avx512fp16`, `avx512ifma`, `avx512vbmi`, `avx512vbmi2`, `avx512vl`, `avx512vnni`, `avx512vp2intersect`, and `avx512vpopcntdq` and 267 more
    = help: consider using a Cargo feature instead
    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
             [lints.rust]
             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(target_feature, values("vector-enhancements-2"))'] }
    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(target_feature, values(\"vector-enhancements-2\"))");` to the top of the `build.rs`
    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
    = note: `-D unexpected-cfgs` implied by `-D warnings`
    = help: to override `-D warnings` add `#[allow(unexpected_cfgs)]`

error: unexpected `cfg` condition value: `vector-enhancements-2`
   --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:820:19
    |
820 |         all(test, target_feature = "vector-enhancements-2"),
    |                   ^^^^^^^^^^^^^^^^^-----------------------
    |                                    |
    |                                    help: there is a expected value with a similar name: `"vector-enhancements-1"`
    |
    = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-int8`, `amx-tile`, `atomics`, `avx`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, `avx512f`, `avx512fp16`, `avx512ifma`, `avx512vbmi`, `avx512vbmi2`, `avx512vl`, `avx512vnni`, `avx512vp2intersect`, and `avx512vpopcntdq` and 267 more
    = help: consider using a Cargo feature instead
    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
             [lints.rust]
             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(target_feature, values("vector-enhancements-2"))'] }
    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(target_feature, values(\"vector-enhancements-2\"))");` to the top of the `build.rs`
    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration

error: unexpected `cfg` condition value: `vector-enhancements-2`
   --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:843:19
    |
843 |         all(test, target_feature = "vector-enhancements-2"),
    |                   ^^^^^^^^^^^^^^^^^-----------------------
    |                                    |
    |                                    help: there is a expected value with a similar name: `"vector-enhancements-1"`
    |
    = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-int8`, `amx-tile`, `atomics`, `avx`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, `avx512f`, `avx512fp16`, `avx512ifma`, `avx512vbmi`, `avx512vbmi2`, `avx512vl`, `avx512vnni`, `avx512vp2intersect`, and `avx512vpopcntdq` and 267 more
    = help: consider using a Cargo feature instead
    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
             [lints.rust]
             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(target_feature, values("vector-enhancements-2"))'] }
    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(target_feature, values(\"vector-enhancements-2\"))");` to the top of the `build.rs`
    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration

error: unexpected `cfg` condition value: `vector-enhancements-2`
   --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:861:19
    |
861 |         all(test, target_feature = "vector-enhancements-2"),
    |                   ^^^^^^^^^^^^^^^^^-----------------------
    |                                    |
    |                                    help: there is a expected value with a similar name: `"vector-enhancements-1"`
    |
    = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-int8`, `amx-tile`, `atomics`, `avx`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, `avx512f`, `avx512fp16`, `avx512ifma`, `avx512vbmi`, `avx512vbmi2`, `avx512vl`, `avx512vnni`, `avx512vp2intersect`, and `avx512vpopcntdq` and 267 more
    = help: consider using a Cargo feature instead
    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
             [lints.rust]
             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(target_feature, values("vector-enhancements-2"))'] }
    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(target_feature, values(\"vector-enhancements-2\"))");` to the top of the `build.rs`
    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration

error: unexpected `cfg` condition value: `vector-enhancements-2`
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:3273:19
     |
3273 |         all(test, target_feature = "vector-enhancements-2"),
     |                   ^^^^^^^^^^^^^^^^^-----------------------
     |                                    |
     |                                    help: there is a expected value with a similar name: `"vector-enhancements-1"`
     |
     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-int8`, `amx-tile`, `atomics`, `avx`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, `avx512f`, `avx512fp16`, `avx512ifma`, `avx512vbmi`, `avx512vbmi2`, `avx512vl`, `avx512vnni`, `avx512vp2intersect`, and `avx512vpopcntdq` and 267 more
     = help: consider using a Cargo feature instead
     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
              [lints.rust]
              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(target_feature, values("vector-enhancements-2"))'] }
     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(target_feature, values(\"vector-enhancements-2\"))");` to the top of the `build.rs`
     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration

error: unexpected `cfg` condition value: `vector-enhancements-2`
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:3283:19
     |
3283 |         all(test, target_feature = "vector-enhancements-2"),
     |                   ^^^^^^^^^^^^^^^^^-----------------------
     |                                    |
     |                                    help: there is a expected value with a similar name: `"vector-enhancements-1"`
     |
     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-int8`, `amx-tile`, `atomics`, `avx`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, `avx512f`, `avx512fp16`, `avx512ifma`, `avx512vbmi`, `avx512vbmi2`, `avx512vl`, `avx512vnni`, `avx512vp2intersect`, and `avx512vpopcntdq` and 267 more
     = help: consider using a Cargo feature instead
     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
              [lints.rust]
              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(target_feature, values("vector-enhancements-2"))'] }
     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(target_feature, values(\"vector-enhancements-2\"))");` to the top of the `build.rs`
     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration

error: unexpected `cfg` condition value: `vector-enhancements-2`
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/macros.rs:31:30
     |
31   |         #[cfg_attr(all(test, target_feature = $tf), assert_instr($instr))]
     |                              ^^^^^^^^^^^^^^^^^---
     |                                               |
     |                                               help: there is a expected value with a similar name: `"vector-enhancements-1"`
     |
    ::: library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:3390:5
     |
3390 |     test_impl! { vcgsb (a: vector_float) -> vector_signed_int [simd_cast, "vector-enhancements-2" vcgsb] }
     |     ------------------------------------------------------------------------------------------------------ in this macro invocation
     |
     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-int8`, `amx-tile`, `atomics`, `avx`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, `avx512f`, `avx512fp16`, `avx512ifma`, `avx512vbmi`, `avx512vbmi2`, `avx512vl`, `avx512vnni`, `avx512vp2intersect`, and `avx512vpopcntdq` and 267 more
     = help: consider using a Cargo feature instead
     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
              [lints.rust]
              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(target_feature, values("vector-enhancements-2"))'] }
     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(target_feature, values(\"vector-enhancements-2\"))");` to the top of the `build.rs`
     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
     = note: this error originates in the macro `test_impl` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `vector-enhancements-2`
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/macros.rs:31:30
     |
31   |         #[cfg_attr(all(test, target_feature = $tf), assert_instr($instr))]
     |                              ^^^^^^^^^^^^^^^^^---
     |                                               |
     |                                               help: there is a expected value with a similar name: `"vector-enhancements-1"`
     |
    ::: library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:3402:5
     |
3402 |     test_impl! { vclgsb (a: vector_float) -> vector_unsigned_int [simd_cast, "vector-enhancements-2" vclgsb] }
     |     ---------------------------------------------------------------------------------------------------------- in this macro invocation
     |
     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-int8`, `amx-tile`, `atomics`, `avx`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, `avx512f`, `avx512fp16`, `avx512ifma`, `avx512vbmi`, `avx512vbmi2`, `avx512vl`, `avx512vnni`, `avx512vp2intersect`, and `avx512vpopcntdq` and 267 more
     = help: consider using a Cargo feature instead
     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
              [lints.rust]
              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(target_feature, values("vector-enhancements-2"))'] }
     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(target_feature, values(\"vector-enhancements-2\"))");` to the top of the `build.rs`
     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
     = note: this error originates in the macro `test_impl` (in Nightly builds, run with -Z macro-backtrace for more info)

error: the feature named `vector-packed-decimal` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:4778:18
     |
4778 | #[target_feature(enable = "vector-packed-decimal")]
     |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-packed-decimal` is not valid for this target

error: the feature named `vector-packed-decimal` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:4787:18
     |
4787 | #[target_feature(enable = "vector-packed-decimal")]
     |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-packed-decimal` is not valid for this target

error: the feature named `vector-packed-decimal` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:4796:18
     |
4796 | #[target_feature(enable = "vector-packed-decimal")]
     |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-packed-decimal` is not valid for this target

error: the feature named `vector-packed-decimal` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:4804:18
     |
4804 | #[target_feature(enable = "vector-packed-decimal")]
     |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-packed-decimal` is not valid for this target

error: the feature named `vector-packed-decimal` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:4812:18
     |
4812 | #[target_feature(enable = "vector-packed-decimal")]
     |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-packed-decimal` is not valid for this target

error: the feature named `vector-packed-decimal` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:4820:18
     |
4820 | #[target_feature(enable = "vector-packed-decimal")]
     |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-packed-decimal` is not valid for this target

error: the feature named `vector-packed-decimal` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:4828:18
     |
4828 | #[target_feature(enable = "vector-packed-decimal")]
     |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-packed-decimal` is not valid for this target

error: the feature named `vector-packed-decimal` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:4836:18
     |
4836 | #[target_feature(enable = "vector-packed-decimal")]
     |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-packed-decimal` is not valid for this target

error: the feature named `vector-enhancements-1` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:4922:18
     |
4922 | #[target_feature(enable = "vector-enhancements-1")]
     |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-enhancements-1` is not valid for this target

error: the feature named `vector-enhancements-1` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:5083:18
     |
5083 | #[target_feature(enable = "vector-enhancements-1")]
     |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-enhancements-1` is not valid for this target

error: the feature named `vector-enhancements-1` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:5094:18
     |
5094 | #[target_feature(enable = "vector-enhancements-1")]
     |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-enhancements-1` is not valid for this target

error: the feature named `vector-enhancements-1` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:5167:18
     |
5167 | #[target_feature(enable = "vector-enhancements-1")]
     |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-enhancements-1` is not valid for this target

error: the feature named `vector-enhancements-2` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:5206:18
     |
5206 | #[target_feature(enable = "vector-enhancements-2")]
     |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-enhancements-2` is not valid for this target

error: the feature named `vector-enhancements-2` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:5215:18
     |
5215 | #[target_feature(enable = "vector-enhancements-2")]
     |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-enhancements-2` is not valid for this target

error: the feature named `vector-enhancements-2` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:3508:38
     |
3508 |                       #[target_feature(enable = "vector-enhancements-2")]
     |                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-enhancements-2` is not valid for this target
...
3528 | /     impl_vec_sld! {
3529 | |         vector_signed_char
3530 | |         vector_bool_char
3531 | |         vector_unsigned_char
...    |
3546 | |         vector_double
3547 | |     }
     | |_____- in this macro invocation
     |
     = note: this error originates in the macro `impl_vec_sld` (in Nightly builds, run with -Z macro-backtrace for more info)

error: the feature named `vector-enhancements-2` is not valid for this target
    --> library/core/src/../../stdarch/crates/core_arch/src/s390x/vector.rs:3518:38
     |
3518 |                       #[target_feature(enable = "vector-enhancements-2")]
     |                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `vector-enhancements-2` is not valid for this target
...
3528 | /     impl_vec_sld! {
3529 | |         vector_signed_char
3530 | |         vector_bool_char
3531 | |         vector_unsigned_char
...    |
3546 | |         vector_double
3547 | |     }
     | |_____- in this macro invocation
     |
     = note: this error originates in the macro `impl_vec_sld` (in Nightly builds, run with -Z macro-backtrace for more info)

error: could not document `core`
warning: build failed, waiting for other jobs to finish...
[RUSTC-TIMING] core test:false 12.624
Command has failed. Rerun with -v to see more details.
Build completed unsuccessfully in 0:00:13
  local time: Thu Apr  3 12:36:48 UTC 2025
  network time: Thu, 03 Apr 2025 12:36:49 GMT
##[error]Process completed with exit code 1.
Post job cleanup.

[Amanieu]

These features are for the various AVX512 sub-features. We have already stabilized some of these names in is_x86_feature_detected! so the language level name should match.