Tracking Issue for `bf16` type in stdarch avx512
Open
Nobody has claimed this yet.
C-tracking-issue
O-x86_32
O-x86_64
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(stdarch_x86_avx512_bf16)]
This is a tracking issue for the bf16 type in stdarch. This is just a wrapper around u16, but it makes the intrinsic signatures more readable.
Public API
The bf16 type in core::arch::x86 and core::arch::x86_64, and its associated functions in avx512bf16 and avxneconvert
Steps / History
- Final comment period (FCP)^1
- 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 with the stdarch_x86_avx512_bf16 feature gate and the public API in core::arch::x86 and core::arch::x86_64, including the associated functions in avx512bf16 and avxneconvert. Done is represented by completing the final comment period and opening a stabilization PR.
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
- 20/100