Hardware support
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 Firefox hardware dashboard and the Firefox Graphics telemetry view linked as [1] and [2]. Check whether mobile usage data is available, then establish accurate support percentages for ARMv8-A NEON fp16, F16C, and AVX-512 fp16; the issue is done when those figures are reported clearly.
Written by the indexing model from the issue text.
Description
I'm trying to quantify what percentage of Firefox users could actually use this proposal.
Using [1] and [2], here's what I got. Note: this is desktop only data.
For desktop we have ~97% x86/x86_64 usage between Intel/AMD. The remaining ~3% looks like apple silicon if I'm reading right for our only major AArch64 usage.
ARMv8-A NEON fp16 3% implied from Apple Silicon
F16C: No direct data. For Intel it was added in Ivy Bridge. The successor, Haswell, introduced AVX2. We have 82% support for AVX and 72% for AVX2, so I would guess F16C is somewhere between there?
AVX-512 fp16: Only in Xeon, so I'm assuming no usage.
@SPY (or anyone else) do you have any more accurate usage numbers here?
I'm going to see if I can find any mobile usage numbers, but that will take a longer time as our pre-generated dashboards don't see to track this.
[1] https://data.firefox.com/dashboard/hardware
[2] https://firefoxgraphics.github.io/telemetry/#view=system
- 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/half-precision
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
WebAssembly/half-precision#10 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
WebAssembly/half-precision#8 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
WebAssembly/half-precision#6 · 1 comment · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
WebAssembly/half-precision#4 · 22 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in WebAssembly/half-precision
Similar issues
-
I-prioritize needs-triage regression-from-stable-to-beta T-lang
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
rust-lang/rust#163830 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rubys/roundhouse#444 ·
Maintainers usually reply within 1 day
-
crash llvm:codegen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
llvm/llvm-project#229064 ·
Maintainers usually reply within 1 day
-
area:lowering kind:bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
vxc prints a debug line '[flat-codegen] emitted module via the flat path' on every compilePossibly taken @YodHeVauHe claimed this today. Opendevex good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day