WebAssembly / WebAssembly/spec
SIMD test optimization?
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 3.5k
- Forks
- 539
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 13
Description
A lot of the SIMD tests run the same floats through all of the lanes, instead of just assuming lanewise operations to be implemented in a lanewise way. Is there any particular reason to do it this way? You could probably cut down the size of the tests by a factor of 2 or 4 if you just assumed all the lanes behave the same.
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
No file or test path is named. Start by locating the SIMD tests and reviewing how lane inputs are constructed, then determine whether repeated lane values are intentional and whether varying them is required. Done would be an agreed, justified test-size reduction with any affected tests updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100