Adding some additional context:
We're running into this issue in Nixpkgs: https://github.com/NixOS/nixpkgs/pull/264599#pullrequestreview-1707381631.
The GLIBC 2.38 update introduces intrinsics for `aarch64-linux` in `math.h`.
NVCC (NVIDIA's CUDA Compiler) declares itself to be the same compiler as its host compiler. This causes inclusion of unsupported `aarch64-linux` intrinsics. NVCC is now unable to compile any CUDA file for `aarch64-linux` because it does not support these intrinsics: https://forums.developer.nvidia.com/t/nvcc-fails-to-build-with-arm-neon-instructions-cpp-vs-cu/248355/2.
I'll be submitting the same patch I've made for Nixpkgs.
Adding some additional context:
We're running into this issue in Nixpkgs: https:/ /github. com/NixOS/ nixpkgs/ pull/264599# pullrequestrevi ew-1707381631.
The GLIBC 2.38 update introduces intrinsics for `aarch64-linux` in `math.h`.
NVCC (NVIDIA's CUDA Compiler) declares itself to be the same compiler as its host compiler. This causes inclusion of unsupported `aarch64-linux` intrinsics. NVCC is now unable to compile any CUDA file for `aarch64-linux` because it does not support these intrinsics: https:/ /forums. developer. nvidia. com/t/nvcc- fails-to- build-with- arm-neon- instructions- cpp-vs- cu/248355/ 2.
I'll be submitting the same patch I've made for Nixpkgs.