You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The WebAssembly Relaxed SIMD proposal introduces new vector operations that
take advantage of widely available instruction sets to accelerate compute
workloads. The proposal relaxes the strict portability constraints of
the fixed-width SIMD proposal. We're
hoping to ship this in Chrome 105/106 contingent on a Phase 4
(currently at Phase 3) vote in the Wasm CG, requesting a WebKit position for the proposal.
The WebKittens are neutral. The performance looks exciting, and the operations seem pretty reasonable. We are still worried about the burden this places on developers to test against multiple CPUs, and potential compatibility issues that would result from that.
Uh oh!
There was an error while loading. Please reload this page.
Request for position on an emerging web specification
(Please delete inapplicable rows.)
Information about the spec
Design reviews and vendor positions
Bugs tracking this feature
Anything else we need to know
On WebKit-dev, @dtig wrote:
Hi webkit-dev,
The WebAssembly Relaxed SIMD proposal introduces new vector operations that
take advantage of widely available instruction sets to accelerate compute
workloads. The proposal relaxes the strict portability constraints of
the fixed-width
SIMD proposal. We're
hoping to ship this in Chrome 105/106 contingent on a Phase 4
(currently at Phase 3) vote in the Wasm CG, requesting a WebKit position for the proposal.
Proposal: https://github.com/WebAssembly/relaxed-simd
Spec: https://github.com/WebAssembly/relaxed-simd/tree/main/document/core
Implementation status (V8, SpiderMonkey):
https://github.com/WebAssembly/relaxed-simd/blob/main/proposals/relaxed-simd/ImplementationStatus.md
Preliminary performance data that motivated the proposal:
WebAssembly/simd#79
Thanks,
Deepti
The text was updated successfully, but these errors were encountered: