spec
spec copied to clipboard
WebAssembly
WebAssembly specification, reference interpreter, and test suite.
See discussion in https://github.com/WebAssembly/spec/issues/1292#issuecomment-2683583067
I asked this question at https://github.com/emscripten-core/emscripten/discussions/23966 and was told it's a limitation imposed by the spec. In wasm64, the spec caps the maximum memory to 16 GB in https://github.com/WebAssembly/memory64/blob/9003cd5e24e53b84cd9027ea3dd7ae57159a6db1/document/js-api/index.bs#L1785. Could...
### Current status: After the memory64 update, the spec says that ([link](https://webassembly.github.io/memory64/core/valid/types.html#memory-types)): - table limits must be within range `2^addrtype - 1`, i.e. for table32 up to `2^32 - 1`,...
The JS API's [implementation limits](https://www.w3.org/TR/wasm-js-api-2/#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 JS API spec's current handling of implementation limits still has many...
In https://github.com/WebAssembly/spec/issues/1618 : > With the annotations proposal (Wasm 3) we now support string-escaping arbitrary Unicode as identifiers, so I think we can close this. We (W3C i18n WG) have...
We've recently added automatic import of Wasm tests into the [Web Platform Tests](https://github.com/web-platform-tests/wpt/) repo by using the HTML-wrapper output of the [test/build.py](https://github.com/WebAssembly/spec/blob/main/test/build.py) script (see https://github.com/web-platform-tests/wpt/pull/49277). There are several cleanups and...
It often happens that checking the Echinda status too quickly after request upload results in failure (to get the validation results), but checking it shortly after that would result in...
[compile a potential WebAssembly response](https://webassembly.github.io/spec/web-api/#compile-a-potential-webassembly-response) lists separate steps for [upon rejection](https://webidl.spec.whatwg.org/#upon-rejection) and [upon fulfillment](https://webidl.spec.whatwg.org/#upon-fulfillment) which are both specified to call [react](https://webidl.spec.whatwg.org/#dfn-perform-steps-once-promise-is-settled). The result of following the spec pedantically here is...
1. The third (recursive) case of the binary definition of `sN` should have `i:s` instead of `i:u` - 3.0: https://webassembly.github.io/spec/core/binary/values.html#integers - 2.0 for comparison: https://www.w3.org/TR/wasm-core-2/#integers%E2%91%A4 ------- 2. (arguable?) The module...
Metadata
Owner
Metadata
WebAssembly specification, reference interpreter, and test suite.