Justin Michaud

Can we add text to the spec specifically guaranteeing that 0xFF will not be used for future expansion, and will be left for implementations to use? (see also https://github.com/WebAssembly/design/issues/1141) >...

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,...

Yes, exactly @sbc100. I recall that when this memory mode was introduced, it was a very noticeable performance progression, but I am not sure if this is true for other...

Yes, unfortunately there would be a mandatory mask if we allow authors to specify masks less than 32 bit. This is not needed for my use case, I was just...

Do we have an example of that @programmerjake? I do not know of any such cpu proposal today.

Just so I understand correctly, before, the stack looked like: ``` 0 .... FFFF (growing towards 0) tail calls can grow here | garbage | retN ... ret0 | |...

Commit message draft: This is the first patch to support the WASM SIMD proposal: https://github.com/WebAssembly/simd/blob/main/proposals/simd/SIMD.md 1) Add a feature flag and support for parsing the new SIMD opcodes and the...

> We should keep this runtime flag until the default-on-build is shipped. We need a way to disable them when some problems happen later during the development / releasing. Yes,...

Rebased + renamed things + added @jjgriego 's changes to fix armv7

See https://github.com/WebKit/WebKit/pull/5547