Spec tests with memory offsets
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- wasm
- Domain
- testing
Research direction
Start by locating the spec tests referenced in the issue and inspect existing atomic memory-access cases. Add coverage for constant offsets on memory addresses, then run the relevant spec test suite and confirm it fails for an implementation that ignores those offsets.
Written by the indexing model from the issue text.
Description
While working on implementation of atomics, I noticed that the spec tests from here passed despite the logic being trivially broken by ignoring const offsets on memory addresses. While I don't know what the coverage goal of spec tests is, const offsets seem like they may be worth having tests for to make it easier to write correct implementations.
- Dominant language
- WebAssembly
- Stars
- 767
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
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.
More from WebAssembly/threads
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
WebAssembly/threads#254 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
WebAssembly/threads#253 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
WebAssembly/threads#245 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
WebAssembly/threads#240 ·
-
Branch renaming Open
Difficulty 1/5 Under an hour Newbie friendliness 20/100
WebAssembly/threads#237 ·
All issues in WebAssembly/threads
Similar issues
-
agent/quality hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Flaky storybook test Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
hasadna/open-bus-map-search#1893 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
benchmark-gap
Difficulty 2/5 1-3 hours Newbie friendliness 70/100