-
Notifications
You must be signed in to change notification settings - Fork 27
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
Using simd128 leads to unloadable Wasm on older browsers #94
Comments
Does anyone know a way to implement a fallback so that we can use intrinsics and fall back to the generic version if that fails? Otherwise we might add a feature to force the generic version on wasm for such browsers and the user will either have to supply a browser check to select the best version or live with the suboptimal performance on browsers supporting SIMD. |
@llogiq A Wasm binary that includes unsupported intrinsics can fail to parse, even if it won't use them. This comment is accurate unfortunately BurntSushi/memchr#144 (comment):
The route [target.wasm32-unknown-unknown]
rustflags = ["-Ctarget-feature=+simd128"] Apps can then build multiple binaries, and use feature detection to serve the optimal one. For the foreseeable future this is the only portable option as far as I know. |
I'm also running into this issue. I'm trying to compile a version on my project without simd128 to support down to iOS 15-16.3 but this project is a dependency of a lib I'm using. |
You can use the |
I believe I'm seeing the same as this issue with this crate:
Here's wasm2wat showing the functions at issue:
The text was updated successfully, but these errors were encountered: