-
Notifications
You must be signed in to change notification settings - Fork 644
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
Incorrect Handling of SIMD v128 Return Value #3963
Comments
@Q1IQ SIMD on interp is currently in development. You may want to try again using the development branch. dev/simd_for_interp @Zzzabiyaka @loganek Just FYI. |
Hi |
SIMD is not supported on the fast-jit. Only llvm-jit and aot support SIMD opcodes. |
interp should at least output a hint like "unsupported opcode" similar to fast-jit, instead of directly segmentation fault.
|
I think for fast interp it might not be needed right now given we expect to deliver simd there in about a month or so For classic interp maybe it'd be helpful |
Please re-try with latest commit, like 04f1071. if with (module
(memory 1)
(func $return_v128 (result v128)
(v128.const i32x4 0x00000004 0x34567890 0x66666666 0x77777777)
)
(export "main" (func $return_v128))
) -> $ /workspaces/wasm-micro-runtime/product-mini/platforms/linux/build/iwasm --interp -f main case1.wasm
Exception: unsupported opcode if with (module
(memory 1)
(func $func1 (result i32)
i32.const 1234
)
(export "main" (func $func1))
) -> $ /workspaces/wasm-micro-runtime/product-mini/platforms/linux/build/iwasm --interp -f main case2.wasm
Exception: unsupported opcode |
Subject of the issue
iwasm fails to handle v128 return values correctly
Test case
program.wasm.txt
Your environment
iwasm --interp ./program.wasm
Steps to reproduce
Run the following wasm module:
Observed output:
Expected behavior
The
v128
value should be returned correctly, like it can correctly process i32.The text was updated successfully, but these errors were encountered: