Contact emailsSpecOverview document: https://github.com/WebAssembly/simd/blob/master/proposals/simd/SIMD.mdProposal directory: https://github.com/WebAssembly/simd/tree/master/proposals/simdSummaryThe WebAssembly SIMD proposal defines a portable, performant subset of SIMD operations that map to vector instructions that are available across most modern hardware platforms.This is purely a WebAssembly performance feature that adds WebAssembly operations and does not affect web API behavior, but is still useful for developers to be aware of as it can change performance characteristics of applications using WebAssembly.An Origin Trial for WebAssembly SIMD started in Chrome 84 and is scheduled to end in Chrome 86. We then extended it to Chrome 88. The results of the Origin Trial are:- gaps identified in V8 and Emscripten toolchain, bugs, optimization opportunities- identified a use case for for runtime feature detection of supported instructions, design is underwayWe are not ready to ship this, and still need more feedback:new instructions merged into the proposal and have yet to be in OT (such as https://github.com/WebAssembly/simd/pull/127 and https://github.com/WebAssembly/simd/pull/237)
Link to “Intent to Prototype” blink-dev discussionGoals for experimentationNew instructions added to the proposal, so we would like some time for developers to update their code base, examine the usefulness and performance of the new instructions, and for us to incorporate feedback in implementation or specification.Experimental timelineM89-M90Any risks when the experiment finishes?Performance loss from not using SIMD.Reason this experiment is being extendedNew instructions merged into the proposal and have yet to be in OT (such as https://github.com/WebAssembly/simd/pull/127 and https://github.com/WebAssembly/simd/pull/237). Need time for developers to upgrade and try this out.Ongoing technical constraintsNone.DebuggabilityDevtools is actively working on Wasm debuggability, and SIMD instructions are supported.Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?Yes.Link to entry on the feature dashboard
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/990cdfae-a3e0-4cd4-9623-fc733c533a91n%40chromium.org.
My main concern is extending the origin trial twice and running it for a long time. But if the API is indeed evolving and there is excellent feedback, that could alleviate my concern.On Tue, Nov 10, 2020 at 4:57 PM Zhi An Ng <zh...@chromium.org> wrote:Contact emailsSpecOverview document: https://github.com/WebAssembly/simd/blob/master/proposals/simd/SIMD.mdProposal directory: https://github.com/WebAssembly/simd/tree/master/proposals/simdSummaryThe WebAssembly SIMD proposal defines a portable, performant subset of SIMD operations that map to vector instructions that are available across most modern hardware platforms.This is purely a WebAssembly performance feature that adds WebAssembly operations and does not affect web API behavior, but is still useful for developers to be aware of as it can change performance characteristics of applications using WebAssembly.An Origin Trial for WebAssembly SIMD started in Chrome 84 and is scheduled to end in Chrome 86. We then extended it to Chrome 88. The results of the Origin Trial are:- gaps identified in V8 and Emscripten toolchain, bugs, optimization opportunities- identified a use case for for runtime feature detection of supported instructions, design is underwayWe are not ready to ship this, and still need more feedback:new instructions merged into the proposal and have yet to be in OT (such as https://github.com/WebAssembly/simd/pull/127 and https://github.com/WebAssembly/simd/pull/237)The previous extension also mentioned additional instructions being added. Are these new instructions ones on top of the other ones? Did the demand for thes instructions come directly from experience in the origin trial?
Link to “Intent to Prototype” blink-dev discussionGoals for experimentationNew instructions added to the proposal, so we would like some time for developers to update their code base, examine the usefulness and performance of the new instructions, and for us to incorporate feedback in implementation or specification.Experimental timelineM89-M90Any risks when the experiment finishes?Performance loss from not using SIMD.Reason this experiment is being extendedNew instructions merged into the proposal and have yet to be in OT (such as https://github.com/WebAssembly/simd/pull/127 and https://github.com/WebAssembly/simd/pull/237). Need time for developers to upgrade and try this out.Ongoing technical constraintsNone.DebuggabilityDevtools is actively working on Wasm debuggability, and SIMD instructions are supported.Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?Yes.Link to entry on the feature dashboard--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/990cdfae-a3e0-4cd4-9623-fc733c533a91n%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAP2LTJ0vi%2BG58vook-G%3D5%3DRevrdZ-oD3CYZiz7CU3oLk%2BLZ0RA%40mail.gmail.com.