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
{{ message }}
This repository has been archived by the owner on Jul 1, 2023. It is now read-only.
iOS platforms do not support certain primitives needed for fast JITing in applications distributed through the App Store. JITing is needed for a fast wasm runtime.
Wasmer added support for precompilation through which wasm can be compiled to a dylib and that dylib can then be bundled with applications to allow distribution through the App Store.
There are other wasm runtimes that interpret wasm and do not depend on JITing. The catch is that they are slower than JITed runtimes and I'm not sure if applications that interpret wasm are allowed on the App Store.
So either:
the API for compiling wasm will need to be adjusted to support precompilation on iOS platforms
or wasm will need to be intrepreted on iOS through e.g. wasm3
or we'll have to wait until Apple adds first party wasm support (I have no reason to assume that they have plans to do so)
or no iOS support
The text was updated successfully, but these errors were encountered:
iOS platforms do not support certain primitives needed for fast JITing in applications distributed through the App Store. JITing is needed for a fast wasm runtime.
Wasmer added support for precompilation through which wasm can be compiled to a dylib and that dylib can then be bundled with applications to allow distribution through the App Store.
There are other wasm runtimes that interpret wasm and do not depend on JITing. The catch is that they are slower than JITed runtimes and I'm not sure if applications that interpret wasm are allowed on the App Store.
So either:
The text was updated successfully, but these errors were encountered: