aboutsummaryrefslogtreecommitdiff
path: root/compiler-rt
diff options
context:
space:
mode:
authorJeremy Morse <jeremy.morse@sony.com>2024-01-23 16:51:47 +0000
committerJeremy Morse <jeremy.morse@sony.com>2024-01-23 16:58:31 +0000
commit5176df55d3afcbecd6e6c42176fa7175897f0016 (patch)
tree06ed594bbb9b34e87e54188fab5b4b721bca0904 /compiler-rt
parent1f6f19935c1b4512190f1bc94ebf94f3d2b69911 (diff)
downloadllvm-5176df55d3afcbecd6e6c42176fa7175897f0016.zip
llvm-5176df55d3afcbecd6e6c42176fa7175897f0016.tar.gz
llvm-5176df55d3afcbecd6e6c42176fa7175897f0016.tar.bz2
[CompilerRT] Attempt to fix a lit-config issue
This is a follow-up to 3112578597c03 -- it looks like passing the added cmake flag to pythonize_bool also appends "_PYBOOL" to the flag name, which this lit config file is missing. This trips up builds such as: https://lab.llvm.org/buildbot/#/builders/275/builds/3661 https://lab.llvm.org/buildbot/#/builders/184/builds/9811 Where COMPILER_RT_HAS_AARCH64_SME ends up expanding to nothing.
Diffstat (limited to 'compiler-rt')
-rw-r--r--compiler-rt/test/lit.common.configured.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/compiler-rt/test/lit.common.configured.in b/compiler-rt/test/lit.common.configured.in
index b93e20e..db5d7c5 100644
--- a/compiler-rt/test/lit.common.configured.in
+++ b/compiler-rt/test/lit.common.configured.in
@@ -50,7 +50,7 @@ set_default("gwp_asan", @COMPILER_RT_HAS_GWP_ASAN_PYBOOL@)
set_default("expensive_checks", @LLVM_ENABLE_EXPENSIVE_CHECKS_PYBOOL@)
set_default("test_standalone_build_libs", @COMPILER_RT_TEST_STANDALONE_BUILD_LIBS_PYBOOL@)
set_default("has_compiler_rt_libatomic", @COMPILER_RT_BUILD_STANDALONE_LIBATOMIC_PYBOOL@)
-set_default("aarch64_sme", @COMPILER_RT_HAS_AARCH64_SME@)
+set_default("aarch64_sme", @COMPILER_RT_HAS_AARCH64_SME_PYBOOL@)
# True iff the test suite supports ignoring the test compiler's runtime library path
# and using `config.compiler_rt_libdir` instead. This only matters when the runtime
# library paths differ.