rust/compiler/rustc_target at f33b5cb590ed4cf520b30dc0c6ea07f9f49299e5 - rust

mirror of https://github.com/rust-lang/rust.git synced 2026-04-27 18:57:42 +03:00

Files

T

Jonathan Brouwer f85b70f2eb Rollup merge of #153068 - sayantn:avxvnni, r=Amanieu

Require avxvnni for avx10.2

AVX10.2 supports masked (and 512-bit) versions of some intrinsics available in AVXVNNI, AVXVNNIINT8 and AVXVNNIINT16 (e.g. AVX10.2 introduces `_mm{,256,512}_{mask{z}}_dpbuud_epi32` corresponding to `_mm{,256}_dpbuud_epi32` from AVXVNNIINT8). But Intel (being Intel), didn't (at least not in SDM) enforce that AVX10.2 (or at least AVX10_VNNI_INT, which is a "discrete AVX10 feature", introduced alongside AVX10.2, and expected to house more such instructions) requires AVXVNNI etc.

To make this (admittedly very Intel) situation a bit better, we can just require these features from the Rust frontend

r? @Amanieu

This also corrects a mistake in std-detect which allowed AVX10 to be enabled without AVX512F, in the (odd) case when F16C or FMA are not available (we require these for AVX512F because otherwise the LLVM assembler doesn't work)

2026-03-26 00:23:10 +01:00

src

Rollup merge of #153068 - sayantn:avxvnni, r=Amanieu

2026-03-26 00:23:10 +01:00

Cargo.toml

Add --print target-spec-json-schema

2025-09-12 20:53:28 +02:00

README.md

Fix outdated crate names in compiler docs

2021-04-08 11:12:14 -05:00

README.md

rustc_target contains some very low-level details that are specific to different compilation targets and so forth.

For more information about how rustc works, see the rustc dev guide.