You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support for the WASM SIMD opcodes in the interpreters.
For my use case I imagine I would use only ARM NEON intrinsics that can run on ARMv7 processors.
I imagine I can create some stub functions and then implement them for arm and keep x86 disabled for now.
Benefit
Ability to run code that uses the SIMD 128 opcodes in the interpreters where AOT is not possible.
Implementation
I've implemented a few of the SIMD opcodes already as a PoC but I'm expecting to work through the list and add them all.
Alternatives
The text was updated successfully, but these errors were encountered:
Thanks @jammar1 . Do you think it'd be good to setup a dev branch so you can post incremental Pull requests or you'd rather just make one big request with all the opcodes implemented? cc: @wenyongh
Agree with using a dev branch. I imagine I will work through each of the SIMD test suites and raise a PR for each opcode in the block's here: core/iwasm/interpreter/wasm_opcode.h.
Feature
Add support for the WASM SIMD opcodes in the interpreters.
For my use case I imagine I would use only ARM NEON intrinsics that can run on ARMv7 processors.
I imagine I can create some stub functions and then implement them for arm and keep x86 disabled for now.
Benefit
Ability to run code that uses the SIMD 128 opcodes in the interpreters where AOT is not possible.
Implementation
I've implemented a few of the SIMD opcodes already as a PoC but I'm expecting to work through the list and add them all.
Alternatives
The text was updated successfully, but these errors were encountered: