AFAICT, the current EMSDK (1.39.19) uses the finalized opcodes for the simd128 feature set, but the version of Node that is included in the EMSDK does not. This makes for amusing runtime errors if you try to compile wasm and test via Node.
- If this is in fact the case (and not a stupid config error on my part), may I suggest that the EMSDK release notes point this out? (Maybe most folks aren't relying on Node for wasm-testing purposes, but it's handy and seems like it would be in sync, since it's included...) - Is there any ETA for when a stable version of Node with final wasm-simd support will be available? - If there is no ETA, are there other fast (non-browser) command-line wasm implementations that would be suitable for testing (ie up to date with the final spec)? (WABT's wasm-interp tool would be great but is too slow for some of my purposes) -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAM%3Ddnvc9HJtUQ69mb_RNXKRxq9Quz8tfQy6v7s04oMvpLu2Efw%40mail.gmail.com.
