summaryrefslogtreecommitdiffstats
path: root/recipes-devtools/python
diff options
context:
space:
mode:
authorKhem Raj <khem.raj@oss.qualcomm.com>2026-10-24 23:18:54 -0700
committerKhem Raj <raj.khem@gmail.com>2026-10-27 19:56:45 -0700
commitc69e53d4adf827821fbcddd4ae07c629327723ee (patch)
tree2aceb051e8f046948fa0eff1393f40ea55c47479 /recipes-devtools/python
parenta2c51ce7e4b582a358b707e5c144c05690d2cf71 (diff)
downloadmeta-clang-c69e53d4adf827821fbcddd4ae07c629327723ee.tar.gz
nonclangable.conf: Stop forcing RVV for python3-numpy on riscv
Appending -march=rv64gcv (rv32gcv) to TOOLCHAIN_OPTIONS made every object in numpy require the vector extension, not just its RVV dispatch targets. On rv64gc tunes the result crashes with SIGILL as soon as _multiarray_umath is loaded on a CPU or kernel without V, e.g. a std::unordered_map constructor in a static initializer is vectorised: vsetivli zero,2,e64,m1,ta,ma This breaks the python3-fsspec ptest (via pandas -> numpy) on qemuriscv64, whose linux-yocto kernel has CONFIG_RISCV_ISA_V unset. numpy's meson build already compiles the RVV dispatch sources with -march=rv64gcv on its own (baseline: none, dispatch: RVV), and the highway __riscv_vsetvl_e8mf8 error this worked around for numpy 2.2.3 no longer happens with numpy 2.5.4 and clang 23. AI-Generated: Uses Claude Code Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Diffstat (limited to 'recipes-devtools/python')
0 files changed, 0 insertions, 0 deletions