Skip to content

WebAssembly Relaxed SIMD #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
marcoscaceres opened this issue Jun 29, 2022 · 2 comments
Closed

WebAssembly Relaxed SIMD #4

marcoscaceres opened this issue Jun 29, 2022 · 2 comments

Comments

@marcoscaceres
Copy link
Contributor

marcoscaceres commented Jun 29, 2022

Request for position on an emerging web specification

(Please delete inapplicable rows.)

  • WebKittens who can provide input:

Information about the spec

Design reviews and vendor positions

  • TAG Design Review:
  • Mozilla standards-positions issue:

Bugs tracking this feature

  • WebKit Bugzilla:
  • Radar:

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

@justinmichaud
Copy link

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.

Thanks again for reaching out!

@hober
Copy link
Member

hober commented Mar 23, 2023

Closing as we've identified our position.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

5 participants