issues Search Results · repo:WebAssembly/spec language:WebAssembly
Filter by
621 results
(77 ms)621 results
inWebAssembly/spec (press backspace or delete to remove)I m not certain if this question has been answered or clarified before (I couldn t find one), so please inform me if
there s been a similar discussion, and I will close this query.
The issue arises on ...
lum1n0us
- 1
- Opened yesterday
- #1869
masterGoverment
- Opened 24 days ago
- #1865
The JS API s implementation limits were introduced in https://github.com/WebAssembly/spec/pull/873 and modified in
https://github.com/WebAssembly/spec/pull/1195 to include runtime limits. However, the ...
bvisness
- 2
- Opened 29 days ago
- #1863
In https://wpt.fyi/results/wasm/jsapi/global/constructor.any.html?label=experimental label=master aligned
Each major browser passes the subtests Explicit value undefined for type {f32, f64, i64}, which ...
ADKaster
- 1
- Opened on Dec 23, 2024
- #1861
We ve recently added automatic import of Wasm tests into the Web Platform Tests repo by using the HTML-wrapper output of
the test/build.py script (see https://github.com/web-platform-tests/wpt/pull/49277). ...
dschuff
- 1
- Opened on Dec 20, 2024
- #1860
When decoding an element section according to 5.5.12. Element Section, the segment type is incorrectly listed as func
(ref func) for case 4. This is covered under elem.wast and should be (ref null func) ...
kelnishi
- 4
- Opened on Dec 9, 2024
- #1854
Hello. I am currently creating an interpreter for WebAssembly 2.0 and have a question about the specification of LEB128.
In the binary-leb128 tests, there is the following test case. From my understanding, ...
chobie
- 2
- Opened on Dec 8, 2024
- #1853
Current status:
After the memory64 update, the spec says that (link):
- table limits must be within range 2^addrtype - 1, i.e. for table32 up to 2^32 - 1, for table64 up to 2^64 - 1;
- memory limits ...
evicy
- 3
- Opened on Nov 13, 2024
- #1864
I m the author of pywasm. I m trying to introduce more friendly error messages in my project, but I found some
inconsistencies.
From spec/interpreter, the uninitialized element error should include the ...
mohanson
- 4
- Opened on Nov 13, 2024
- #1846
The correct types for v128.storeN_lane are [i32 v128] - []. The prose in section 3.3.7.9. has Then the instruction is
valid with type [i32 v128]→[v128].
The formal notation is correct.
kelnishi
- 1
- Opened on Nov 12, 2024
- #1844
![Issue origami icon](/images/modules/search/issues.png)
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Press the /
key to activate the search input again and adjust your query.![Issue origami icon](/images/modules/search/issues.png)
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Press the /
key to activate the search input again and adjust your query.