-
Notifications
You must be signed in to change notification settings - Fork 292
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
Implement the Wasm simd
proposal
#1364
Comments
Will it be possible to deterministically execute wasm with simd? |
@ZheniaZuser yes, since the Wasm |
So, relaxed one will not be deterministic in Wasmi? (Perhaps this could be done with emulation of |
I cannot really say that because I have not yet taken a deep look at it. What I can say that everything that can be implemented deterministically, will be. |
This is about adding support for the
simd
Wasm proposal.The
simd
Wasm proposal has been stabilized (Phase 5) since a long time now. Many Wasm producers already can producesimd
capable Wasm binaries and it is likely to gain even more traction.Wasmi originally did not intend to support
simd
and was hoping for an eventual uptake of the alternativeflexible-vectors
Wasm proposal. However, it seems unlikely at this point that the alternative design will see significant development in the near to medium future.Having
simd
support inwasmi
is the final missing Wasm proposal required to make Wasmi Wasm 2.0 compatible which would be great for advertisement. Obviously,simd
users could use Wasmi. In some past tests we actually saw decreased file sizes by usingsimd
proposal when generating Wasm, so it might also have a nice side benefit. Especially Wasm based game engines that rely on Wasmi might findsimd
support very useful.Due to the massive size of the Wasm
simd
proposal it will be put behind a crate feature flagsimd
. This is important for users who do not needsimd
support as this will significantly impact Wasmi compile time and Wasm execution performance as well as memory usage during Wasm execution.The text was updated successfully, but these errors were encountered: