summaryrefslogtreecommitdiff
path: root/.github
diff options
context:
space:
mode:
authorSayed Adel <seiko@imavr.com>2022-06-15 15:41:11 +0200
committerSayed Adel <seiko@imavr.com>2022-06-15 21:07:44 +0200
commit91faeaa4a615948b1b91853629242b371030b502 (patch)
tree50f50ae3f9e63d8b3bbeeb3a5c55b36cebbd6f30 /.github
parent118e6c433a9afdefbfad7652f56e2b97e23bc508 (diff)
downloadnumpy-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 '.github')
-rw-r--r--.github/workflows/build_test.yml2
1 files changed, 2 insertions, 0 deletions
diff --git a/.github/workflows/build_test.yml b/.github/workflows/build_test.yml
index e1bd519df..c8f542123 100644
--- a/.github/workflows/build_test.yml
+++ b/.github/workflows/build_test.yml
@@ -61,6 +61,8 @@ jobs:
strategy:
matrix:
python-version: ["3.9", "3.10", "3.11-dev"]
+ env:
+ EXPECT_CPU_FEATURES: "SSE SSE2 SSE3 SSSE3 SSE41 POPCNT SSE42 AVX F16C FMA3 AVX2 AVX512F AVX512CD AVX512_KNL AVX512_KNM AVX512_SKX AVX512_CLX AVX512_CNL AVX512_ICL"
steps:
- uses: actions/checkout@v3
with: