Performance with only F16C extension

Open
#8 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
wasm
Domain
performance

Research direction

Start by reading issue #7 and the discussion of the F16C-only lowerings. Identify how the expected slow-down should be measured and what comparison baseline is intended. Done means providing a supported performance estimate for users limited to F16C.

Written by the indexing model from the issue text.

Description

Motivated by #7, what is the expected slow-down for the F16C-only lowerings?

It seems like the majority of our users would be using this path.

Dominant language
WebAssembly
Stars
14
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WebAssembly/fp16

All issues in WebAssembly/fp16

Similar issues

More Performance issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.