Tracking Issue for AVX512_FP16 intrinsics
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_f16)]
This is the tracking issue for the AVX512_FP16 (and related AVX_NE_CONVERT) intrinsics. This depends on the following features
- #111137
- #116909
Public API
This feature covers all of the intrinsics from the avx512fp16 feature and some remaining intrinsics from the avxneconvert feature (more specifically, the __m128h, __m256h and __m512h types, and all intrinsics that use those types or have a f16 parameter)
Implementation History
- rust-lang/stdarch#1605
Steps
- Final Comment Period (FCP)
- Stabilization PR
Unresolved Questions
None yet
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 by reviewing the public API described for the stdarch_x86_avx512_f16 feature gate, the dependent issues #111137 and #116909, and the implementation history in rust-lang/stdarch#1605. The tracking issue considers the work complete only after Final Comment Period and a stabilization PR, but it does not identify a newcomer-sized implementation task.
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