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
Add extism_load_v128/extism_store_v128 #594
Comments
This looks interesting. I'll take it up |
@OLUWAMUYIWA Great! Last time I looked into it I had some issues getting Rust to reliably generate v128 values when compiling to wasm, so I think the first step would be to figure out if it's even possible to reliably use v128 in Rust, then we could try to add these. These new functions would be in the kernel where debugging can get kinda tricky, so it makes sense to do as much as you can on a test project before moving some of the code into the kernel. This also has a larger effects on the PDKs and stuff, so we would need to consider how to roll this out, but since it has the potential to provide significant performance improvements it is definitely worth exploring. |
Thanks for the heads up, @zshipko! |
It struck me that we could possibly achieve this by writing the v128 functions in WAT in a separate module, then using |
That's a good idea! I don't think it would really cause any issues with the verification work. |
We could improve load/store performance by adding
extism_load_v128
,extism_input_load_v128
andextism_store_v128
The text was updated successfully, but these errors were encountered: