Tracking Issue for `stdarch_x86_avx512_vl_u32_to_f32_conversions`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(stdarch_x86_avx512_vl_u32_to_f32_conversions)]
This is a tracking issue for the AVX-512VL intrinsics that convert packed unsigned 32-bit integers to single-precision floating-point values.
These intrinsics correspond to the VCVTUDQ2PS instruction. They are documented in the Intel Software Developer’s Manual, but are not listed in the Intel Intrinsics Guide.
Public API
#[target_feature(enable = "avx512f,avx512vl")]
pub const fn _mm_cvtepu32_ps(a: __m128i) -> __m128 { /* ... */ }
#[target_feature(enable = "avx512f,avx512vl")]
pub const fn _mm_mask_cvtepu32_ps(
src: __m128,
k: __mmask8,
a: __m128i,
) -> __m128 { /* ... */ }
#[target_feature(enable = "avx512f,avx512vl")]
pub const fn _mm_maskz_cvtepu32_ps(
k: __mmask8,
a: __m128i,
) -> __m128 { /* ... */ }
#[target_feature(enable = "avx512f,avx512vl")]
pub const fn _mm256_cvtepu32_ps(a: __m256i) -> __m256 { /* ... */ }
#[target_feature(enable = "avx512f,avx512vl")]
pub const fn _mm256_mask_cvtepu32_ps(
src: __m256,
k: __mmask8,
a: __m256i,
) -> __m256 { /* ... */ }
#[target_feature(enable = "avx512f,avx512vl")]
pub const fn _mm256_maskz_cvtepu32_ps(
k: __mmask8,
a: __m256i,
) -> __m256 { /* ... */ }
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- Implementation https://github.com/rust-lang/stdarch/pull/2197
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
None at this time.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the public API listed in this issue and the implementation in stdarch PR 2197, then read the linked feature-lifecycle stabilization guidance. The tracking work is complete when the final comment period and stabilization PR are finished.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100