Skip to content

Commit a5f3501

Browse files
committed
Bypass PyTorch's SVE+BF16 compile probe when building from source
PyTorch's FindARM.cmake was recently strengthened to hard-fail when its SVE+BF16 compile check doesn't pass. The aarch64 CI image ships gcc-11, which can't compile the probe's mixed NEON/SVE/bfloat16 intrinsics, so `install_pytorch.sh` bails during CMake configure. Executorch's aarch64 runtime targets don't use SVE anyway, so set BUILD_IGNORE_SVE_UNAVAILABLE to keep the Docker build moving. Authored with Claude.
1 parent 28aae26 commit a5f3501

1 file changed

Lines changed: 5 additions & 0 deletions

File tree

.ci/docker/common/install_pytorch.sh

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,11 @@ install_pytorch_and_domains() {
2727
chown -R ci-user .
2828

2929
export _GLIBCXX_USE_CXX11_ABI=1
30+
# PyTorch's FindARM.cmake hard-fails when the SVE+BF16 compile probe
31+
# doesn't pass — gcc-11 in this image is too old to accept the combined
32+
# NEON/SVE/bfloat16 intrinsics the probe exercises. Executorch's aarch64
33+
# runtime targets (phones, embedded) don't use SVE, so bypass the check.
34+
export BUILD_IGNORE_SVE_UNAVAILABLE=1
3035
# Then build and install PyTorch
3136
conda_run python setup.py bdist_wheel
3237
pip_install "$(echo dist/*.whl)"

0 commit comments

Comments
 (0)