-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Passing any of -msse, -msse2, -msse3, -mssse3, -msse4.1, -msse4.2, -mavx, -mfpu=neon flags also requires passing -msimd128 #14132
Comments
Does also passing |
I suspect we'll be seeing more of this unless we adopt #12714. Updating each build system / config is not always an easy change. |
Having a -s ENABLE_EXPERIMENTAL_SIMD128=1 flag that is required to enable -msse (without -msimd128) |
Is there an update on this ? I'm also getting the same problem while trying to compile numpy 1.21.2. This was not a problem when we were compiling numpy 1.17.5 / 1.18.5 but start having the problem from 1.20+. Wonder why would emcc suddenly require a new flag ? PS: I also tried to pass -msimd128 to emcc but it causes another problem, some type could not be found (__m512i, etc). |
Is |
It looks like we don't implement AVX-512 headers that would define |
@tlively Based on the numpy compile options documentation, it seems numpy can select what features to be enabled based on the compiler support: https://numpy.org/devdocs/reference/simd/simd-optimizations.html#build-options-for-compilation. Do you know why it couldn't detect that emcc doesn't support beyond 128bit avx and try to compile with all cpu features ? Also do you know how we can pass the compiler option I tried: But I got the following error:
|
As described here: kaldi-asr/kaldi#4523
I'm getting this error message: em++: error: Passing any of -msse, -msse2, -msse3, -mssse3, -msse4.1, -msse4.2, -mavx, -mfpu=neon flags also requires passing -msimd128!
How to solve the problem?
The text was updated successfully, but these errors were encountered: