diff options
author | Sayed Adel <seiko@imavr.com> | 2022-06-15 15:41:11 +0200 |
---|---|---|
committer | Sayed Adel <seiko@imavr.com> | 2022-06-15 21:07:44 +0200 |
commit | 91faeaa4a615948b1b91853629242b371030b502 (patch) | |
tree | 50f50ae3f9e63d8b3bbeeb3a5c55b36cebbd6f30 /.travis.yml | |
parent | 118e6c433a9afdefbfad7652f56e2b97e23bc508 (diff) | |
download | numpy-91faeaa4a615948b1b91853629242b371030b502.tar.gz |
CI: Guard compile-time CPU features tests
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 gh-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 gh-21750, gh-21748
Diffstat (limited to '.travis.yml')
-rw-r--r-- | .travis.yml | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/.travis.yml b/.travis.yml index d88f401fd..363451ac5 100644 --- a/.travis.yml +++ b/.travis.yml @@ -34,6 +34,8 @@ jobs: - DOWNLOAD_OPENBLAS=1 - NPY_USE_BLAS_ILP64=1 - ATLAS=None + # VSX4 still not supported by ubuntu/gcc-11 + - EXPECT_CPU_FEATURES="VSX VSX2 VSX3" - python: "3.8" os: linux @@ -46,6 +48,7 @@ jobs: - DOWNLOAD_OPENBLAS=1 - NPY_USE_BLAS_ILP64=1 - ATLAS=None + - EXPECT_CPU_FEATURES="VX VXE VXE2" # Wheel builders - python: "3.8" @@ -54,6 +57,7 @@ jobs: virt: vm env: - CIBW_BUILD: cp38-manylinux_aarch64 + - EXPECT_CPU_FEATURES: "NEON NEON_FP16 NEON_VFPV4 ASIMD ASIMDHP ASIMDDP ASIMDFHM" install: python3 -m pip install cibuildwheel==2.4.0 script: | cibuildwheel --output-dir wheelhouse |