-
-
Notifications
You must be signed in to change notification settings - Fork 11k
Neon detection on M1 needs fixing for 1.23.0 release #21747
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
Comments
I noticed one failure compiling
which did not show up prior to #21705
Perhaps it just requires a recast of |
FWIW changing the assignment in double *src2 = (double*)argv[argc-1]; restores the default to
and requested to
|
@dhomeier could you open a PR? |
We do not have a way to catch these errors in CI. Maybe we should have a qemu M1 job that just tests SIMD, like we have for armv7. |
My bad, the current Travis CI are good enough to show up this bug but for somehow I checked armv7 and x86 builds log without paying attention to aarch64 build, I am so sorry for my neglect. Thank you @dhomeier for catching it. |
This guard protects against any sudden unexpected changes that may adversely affect the compile-time SIMD features detection which could leave the SIMD code inactivated. Until now we have faced two cases: 1. Hardening the compile-time test files of Neon/ASIMD features without checking the sanity of the modification leading to disabling all optimizations on aarch64. see numpygh-21747 2. A sudden compiler upgrades by CI side on s390x that causes conflicts with the installed assembler leading to disabling the whole VX/E features, which made us merge SIMD code without testing it. Later, it was discovered that this code disrupted the NumPy build. see numpygh-21750, numpygh-21748
This guard protects against any sudden unexpected changes that may adversely affect the compile-time SIMD features detection which could leave the SIMD code inactivated. Until now we have faced two cases: 1. Hardening the compile-time test files of Neon/ASIMD features without checking the sanity of the modification leading to disabling all optimizations on aarch64. see numpygh-21747 2. A sudden compiler upgrades by CI side on s390x that causes conflicts with the installed assembler leading to disabling the whole VX/E features, which made us merge SIMD code without testing it. Later, it was discovered that this code disrupted the NumPy build. see numpygh-21750, numpygh-21748
This guard protects against any sudden unexpected changes that may adversely affect the compile-time SIMD features detection which could leave the SIMD code inactivated. Until now we have faced two cases: 1. Hardening the compile-time test files of Neon/ASIMD features without checking the sanity of the modification leading to disabling all optimizations on aarch64. see numpygh-21747 2. A sudden compiler upgrades by CI side on s390x that causes conflicts with the installed assembler leading to disabling the whole VX/E features, which made us merge SIMD code without testing it. Later, it was discovered that this code disrupted the NumPy build. see numpygh-21750, numpygh-21748
See #21705 (comment)
The text was updated successfully, but these errors were encountered: