Skip to content
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

Local set and get for V128 #3994

Open
Zzzabiyaka opened this issue Dec 30, 2024 · 0 comments
Open

Local set and get for V128 #3994

Zzzabiyaka opened this issue Dec 30, 2024 · 0 comments

Comments

@Zzzabiyaka
Copy link
Contributor

Zzzabiyaka commented Dec 30, 2024

Hi @wenyongh @lum1n0us @loganek @jammar1
I’m currently implementing local.set / get for v128 to finish off the simd work for fast interpreter

I looked at how it’s done for 32 and 64 bit types and I see that we use separate opcodes for that

https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/core/iwasm/interpreter/wasm_opcode.h#L255

The easiest way for me then would be to add the similar opcode for v128 (EXT_OP_SET_LOCAL_FAST_V128)
and do the handling in fast_interp (extending https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/core/iwasm/interpreter/wasm_loader.c#L12927) , however I have no opcode space (i.e. all 0xc opcodes are already used)

I think my options are pretty much limited to:

  1. Handle WASM_OP_GET_LOCAL in the interpreter (e.g. don’t fast-process it in loader for V128)
  2. Introduce new opcodes like EXT_OP_SET_LOCAL_FAST_V128. I am not sure whether it’s a safe thing to do but I would probably avoid doing it
  3. I probably can emit 2 opcodes EXT_OP_SET_LOCAL_FAST_I64 instead of V128. I think it's going to be quite confusing and risky if possible at all

I think I should stick to option 1 but wanted to gather your opinion first

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant