How should we handle dynamic vector ABIs?
Open
Nobody has claimed this yet.
A-ABI
A-SIMD
C-discussion
E-needs-design
O-AArch64
O-riscv
T-compiler
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
The primary unresolved question of https://github.com/rust-lang/rust/issues/131800 I would say is this edge-case. Opening this marker issue for now, I will explain a bit later but basically: we understand most of the factors here but we need to account for what we actually want to do.
AArch64
- Scalable Vector Extension
- Scalable Matrix Extension: also see https://github.com/rust-lang/rust/issues/133144
RISCV
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 reading the primary unresolved issue, rust-lang/rust#131800, then review the AArch64 scalable vector and matrix extension references and the linked RISC-V V specification. The issue needs a clear decision on how dynamic vector ABIs should be handled and an agreed scope before implementation can be considered done.
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