First-class F16 type and scalar operation
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- wasm
- Domain
- compilers
Research direction
Start with the proposal introduction and the linked CG discussion, then review the exploratory V8 findings about F16 scalar implementation costs. Done means determining whether concrete, persuasive scalar-operation use cases exist and recording a decision about tracking or pursuing the first-class F16 scalar type.
Written by the indexing model from the issue text.
Description
The introduction of the proposal included first-class F16 scalar value type and operations for it.
During exploratory implementation in V8 I discovered it is pretty costly to bring it to V8: there is no instances of 16-bit optional registers/operations, so register allocator, memory allocator and others need significant refactoring. Also, there is no interest in scalar operations from potential users I discussed the proposal with.
Also, during the discussion at CG the same question was raised in chat: "Could we have F16 SIMD shapes without having an F16 scalar type? Similar to i8 and i16 SIMD shapes without i8 and i16 scalar types in the spec so far."
I think I can answer that question now: we don't need them until some concrete and persuading use cases are demonstrated.
Opening that issue for tracking that question.
- Dominant language
- WebAssembly
- Stars
- 14
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from WebAssembly/fp16
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
WebAssembly/fp16#11 · 1 comment · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
WebAssembly/fp16#10 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
WebAssembly/fp16#8 · 1 comment ·
-
Hardware supportOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
WebAssembly/fp16#7 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
WebAssembly/fp16#6 · 1 comment · 1 reaction ·
All issues in WebAssembly/fp16
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
DAE2 crashes on call.without.effects with a non ref.func expressionPossibly taken @stevenfontanella claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
WebAssembly/binaryen#9404 ·
Maintainers usually reply within 1 day
-
area:compiler effort:S impact:med platform:windows type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:Analysis enhancement
Difficulty 1/5 1-3 hours Newbie friendliness 69/100
facebookresearch/atlas-lean#5118 ·
Maintainers usually reply within 1 day
-
C-bugfix
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Quantinuum/hugr#3354 ·
Maintainers usually reply within 1 day