Update relaxed SIMD status for Chrome #284
Conversation
|
So... is it? |
|
Probably not, enable-experimental-webassembly-features implies --wasm-staging, but we need --wasm-experimental-relaxed-simd. I think there might not be a Chrome flag for this yet? @dtig |
|
@ngzhian is right, that this needs to be in wasm-staging, both of these should happen soon though - there's a pending instruction to moving to staging, and I'll be adding a chrome flag for ease of experimentation. So while this PR isn't quite right for now, but it will be applicable soon. Perhaps leave it open and I can merge with the Chrome version where it's supported flagged? |
|
so there's a v8 flag |
|
We do have a chrome flag now (landed in Nov, but I forgot to update this thread). The flag is WebAssemblyRelaxedSimd, and is available from Chrome 110 onwards. |
|
the format for flags in |
|
Interestingly, this page's general format doesn't easily support listing both a version and a flag, since the flag icon replaces the version number in the box. |
Yeah the idea is that if something is under the flag, then people will want to use a flag on a bleeding-edge version of the browser to stay up-to-date with spec anyway, and if something is stable, then minimal version is useful. |
|
I think this isn't "staged" yet, so the flag needs to be |
|
On the website it says |
|
Actually I think https://chromium-review.googlesource.com/c/v8/v8/+/4285497 means that as of Chrome 112, relaxed SIMD should be enabled with the flag in this PR (instead of its own flag). So (assuming that developers are using pre-stable versions of Chromium for testing pre-release wasm features as they should) maybe we should actually merge this. |
|
OK, I just checked and found several recent updates in Chrome and created #328 to cover those, so I think we can actually close this. |
|
#328 has been merged |
5 participants
@dtig I think this is the right flag?