maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/libcxxabi/test/CMakeLists.txt

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

114 lines
3.9 KiB
CMake
Raw Normal View History

[libc++] NFC: Fix incorrect comments in CMake
2021-07-07 21:45:26 +08:00
include(AddLLVM) # for configure_lit_site_cfg and add_lit_testsuite
Add lit configs for libcxxabi tests. This makes running libcxxabi tests on Linux _much_ easier. Adds a check-libcxxabi target to cmake. Also defaults to building a dynamic libc++abi. This is so that the default options still test the libc++abi that is being built. There are two problems with testing a static libc++abi. In the case of a standalone build, the tests will link the system's libc++, which might not have been built against our libc++abi. In the case of an in tree build, libc++ will prefer a dynamic libc++abi from the system over a static libc++abi from the output directory. llvm-svn: 212672
2014-07-10 10:20:11 +08:00
macro(pythonize_bool var)
if (${var})
set(${var} True)
else()
set(${var} False)
endif()
endmacro()
Enable testing for static libc++abi This change leverages framework changes made in libcxx. See those changes for more details. (http://reviews.llvm.org/D16544) Some Mac specific logic for testing against libc++abi had to be moved from libcxxabi's config.py, as it was overriding choices made in libcxx's config.py. That logic is now in libcxx's target_info.py. http://reviews.llvm.org/D16545 llvm-svn: 266729
2016-04-19 20:47:38 +08:00
if (NOT DEFINED LIBCXX_ENABLE_SHARED)
set(LIBCXX_ENABLE_SHARED ON)
endif()
[libcxxabi] Set LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXX to ON if LIBCXX_ENABLE_SHARED is not defined Differential Revision: https://reviews.llvm.org/D71894
2020-01-30 18:05:14 +08:00
option(LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXXABI
"Whether the libc++abi tests should link with the shared libc++abi library"
${LIBCXXABI_ENABLE_SHARED})
option(LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXX
"Whether the libc++abi tests should link with the shared libc++ library"
${LIBCXX_ENABLE_SHARED})
if(LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXXABI AND NOT LIBCXXABI_ENABLE_SHARED)
message(FATAL_ERROR "LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXXABI being ON requires LIBCXXABI_ENABLE_SHARED to be ON")
endif()
if(NOT LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXXABI AND NOT LIBCXXABI_ENABLE_STATIC)
message(FATAL_ERROR "LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXXABI being OFF requires LIBCXXABI_ENABLE_STATIC to be ON")
endif()
if(LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXX AND NOT LIBCXX_ENABLE_SHARED)
message(FATAL_ERROR "LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXX being ON requires LIBCXX_ENABLE_SHARED to be ON")
endif()
if(DEFINED LIBCXX_ENABLE_STATIC
[libc++] Allow specifying arbitrary custom executors with the new format The integration between CMake and executor selection in the new format wasn't very flexible -- only the default executor and SSH executors were supported. This patch makes it possible to specify arbitrary executors with the new format. With the new testing format, a custom executor is just a script that gets called with a command-line to execute, and some arguments like --env, --codesign_identity and --execdir. As such, the default executor is just run.py. Remote execution with the SSH executor can be achived by specifying LIBCXX_EXECUTOR="<path-to-ssh.py> --host <host>". Similarly, arbitrary scripts can be provided.
2020-06-12 03:41:38 +08:00
AND NOT LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXX
[libcxxabi] Set LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXX to ON if LIBCXX_ENABLE_SHARED is not defined Differential Revision: https://reviews.llvm.org/D71894
2020-01-30 18:05:14 +08:00
AND NOT LIBCXX_ENABLE_STATIC)
message(FATAL_ERROR "LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXX being OFF requires LIBCXX_ENABLE_STATIC to be ON")
endif()
Enable testing for static libc++abi This change leverages framework changes made in libcxx. See those changes for more details. (http://reviews.llvm.org/D16544) Some Mac specific logic for testing against libc++abi had to be moved from libcxxabi's config.py, as it was overriding choices made in libcxx's config.py. That logic is now in libcxx's target_info.py. http://reviews.llvm.org/D16545 llvm-svn: 266729
2016-04-19 20:47:38 +08:00
pythonize_bool(LIBCXX_ENABLE_SHARED)
Add lit configs for libcxxabi tests. This makes running libcxxabi tests on Linux _much_ easier. Adds a check-libcxxabi target to cmake. Also defaults to building a dynamic libc++abi. This is so that the default options still test the libc++abi that is being built. There are two problems with testing a static libc++abi. In the case of a standalone build, the tests will link the system's libc++, which might not have been built against our libc++abi. In the case of an in tree build, libc++ will prefer a dynamic libc++abi from the system over a static libc++abi from the output directory. llvm-svn: 212672
2014-07-10 10:20:11 +08:00
pythonize_bool(LIBCXXABI_ENABLE_SHARED)
[libcxxabi] Refactor building and testing libc++abi without threads Summary: This patch adds CMake support for building and testing libc++abi without threads. 1. Add `LIBCXXABI_ENABLE_THREADS` option to CMake. 2. Propagate `LIBCXXABI_ENABLE_THREADS` to lit via lit.site.cfg.in 3. Configure tests for `LIBCXXABI_ENABLE_THREADS=OFF Currently the test suite does not work when libc++abi is built without threads because that information does not propagate to the test suite. Reviewers: danalbert, mclow.lists, jroelofs Reviewed By: jroelofs Subscribers: cfe-commits Differential Revision: http://reviews.llvm.org/D6393 llvm-svn: 222702
2014-11-25 06:42:03 +08:00
pythonize_bool(LIBCXXABI_ENABLE_THREADS)
Add support for building and testing the unwinder. Note: The unwinder currently only works on Darwin and on ARM Linux. Non-ARM Linux support is not yet implemented, and will fail to build. llvm-svn: 212824
2014-07-11 23:36:02 +08:00
pythonize_bool(LIBCXXABI_USE_LLVM_UNWINDER)
[CMake] Update lit test configuration There are several changes: - Don't stringify Pythonized bools (that's why we're Pythonizing them) - Support specifying target and sysroot via CMake variables - Use consistent spelling for --target, --sysroot, --gcc-toolchain llvm-svn: 353137
2019-02-05 12:44:03 +08:00
pythonize_bool(LIBCXXABI_USE_COMPILER_RT)
[libcxxabi] Cleanup and adapt for r291275. NFC. + Now that libcxxabi shares the same threading API as libcxx, a whole chunk of code in src/config.h is made redundant (I missed this earlier). + r291275 split off the externalized-thread-api libcxx configuration from the external-thread-library libcxx configuration. libcxxabi should follow the same approach. llvm-svn: 291440
2017-01-09 19:57:21 +08:00
pythonize_bool(LIBCXXABI_BUILD_EXTERNAL_THREAD_LIBRARY)
[libc++abi] Fix tests when pstl is enabled llvm-svn: 368286
2019-08-08 20:43:20 +08:00
pythonize_bool(LIBCXX_ENABLE_PARALLEL_ALGORITHMS)
[libcxxabi] Allow tests to link with static libc++abi/libc++ even if the shared version is present Summary: Right now the only way to force libc++abi tests to link with the static version of libc++abi is to set `LIBCXXABI_ENABLE_SHARED` to `OFF`. However, this doesn't work when libc++abi is built as standalone project because of [this](https://github.com/llvm/llvm-project/blob/54c522420347e58aa7bae1892cf5c5672b57c875/libcxxabi/CMakeLists.txt#L503-L519). This change allows specifying the version of the library for tests to link with. This is useful for remote testing, for example, with `SSHExecutor`, where we _have_ to link with libc++abi statically. Two new CMake options are introduced here: `LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXXABI` and `LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXX`. They can be set to `OFF` to tell the test utility to link tests with the static libraries. It shouldn't break anything, because the default values of these options are set such that the test utility will behave the same way. Reviewers: EricWF, mclow.lists, phosek, mehdi_amini, ldionne, jroelofs, bcraig Subscribers: mgorny, christof, ldionne, libcxx-commits Tags: #libc Differential Revision: https://reviews.llvm.org/D71894
2019-12-26 17:28:39 +08:00
pythonize_bool(LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXX)
pythonize_bool(LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXXABI)
Add remote testing support to the lit config Now that the corresponding support in libcxx has landed (r230592), adding support here is pretty simple. llvm-svn: 230643
2015-02-26 23:55:01 +08:00
set(LIBCXXABI_TARGET_INFO "libcxx.test.target_info.LocalTI" CACHE STRING
"TargetInfo to use when setting up test environment.")
[libc++] Allow specifying arbitrary custom executors with the new format The integration between CMake and executor selection in the new format wasn't very flexible -- only the default executor and SSH executors were supported. This patch makes it possible to specify arbitrary executors with the new format. With the new testing format, a custom executor is just a script that gets called with a command-line to execute, and some arguments like --env, --codesign_identity and --execdir. As such, the default executor is just run.py. Remote execution with the SSH executor can be achived by specifying LIBCXX_EXECUTOR="<path-to-ssh.py> --host <host>". Similarly, arbitrary scripts can be provided.
2020-06-12 03:41:38 +08:00
set(LIBCXXABI_EXECUTOR "${Python3_EXECUTABLE} ${LIBCXXABI_LIBCXX_PATH}/utils/run.py" CACHE STRING
Add remote testing support to the lit config Now that the corresponding support in libcxx has landed (r230592), adding support here is pretty simple. llvm-svn: 230643
2015-02-26 23:55:01 +08:00
"Executor to use when running tests.")
Add lit configs for libcxxabi tests. This makes running libcxxabi tests on Linux _much_ easier. Adds a check-libcxxabi target to cmake. Also defaults to building a dynamic libc++abi. This is so that the default options still test the libc++abi that is being built. There are two problems with testing a static libc++abi. In the case of a standalone build, the tests will link the system's libc++, which might not have been built against our libc++abi. In the case of an in tree build, libc++ will prefer a dynamic libc++abi from the system over a static libc++abi from the output directory. llvm-svn: 212672
2014-07-10 10:20:11 +08:00
Enable testing for static libc++abi This change leverages framework changes made in libcxx. See those changes for more details. (http://reviews.llvm.org/D16544) Some Mac specific logic for testing against libc++abi had to be moved from libcxxabi's config.py, as it was overriding choices made in libcxx's config.py. That logic is now in libcxx's target_info.py. http://reviews.llvm.org/D16545 llvm-svn: 266729
2016-04-19 20:47:38 +08:00
if (LIBCXXABI_ENABLE_SHARED)
set(LIBCXXABI_TEST_DEPS cxxabi_shared)
else()
set(LIBCXXABI_TEST_DEPS cxxabi_static)
endif()
[libcxxabi] Cleanup and adapt for r291275. NFC. + Now that libcxxabi shares the same threading API as libcxx, a whole chunk of code in src/config.h is made redundant (I missed this earlier). + r291275 split off the externalized-thread-api libcxx configuration from the external-thread-library libcxx configuration. libcxxabi should follow the same approach. llvm-svn: 291440
2017-01-09 19:57:21 +08:00
if (LIBCXXABI_BUILD_EXTERNAL_THREAD_LIBRARY)
[libcxxabi] Introduce an externally threaded libc++abi variant. r281179 Introduced an externally threaded variant of the libc++ library. This patch adds support for a similar library variant for libc++abi. Differential revision: https://reviews.llvm.org/D27575 Reviewers: EricWF llvm-svn: 290888
2017-01-03 20:58:34 +08:00
list(APPEND LIBCXXABI_TEST_DEPS cxx_external_threads)
endif()
[runtimes][NFC] Remove dead code for Standalone builds Standalone builds have been deprecated and then removed for a while now. Trying to use standalone builds leads to a fatal CMake error, so this code is all dead. Remove it to clean things up. Differential Revision: https://reviews.llvm.org/D125561
2022-05-14 00:15:15 +08:00
list(APPEND LIBCXXABI_TEST_DEPS cxx)
if (LIBCXXABI_USE_LLVM_UNWINDER AND TARGET unwind)
list(APPEND LIBCXXABI_TEST_DEPS unwind)
Add support for building and testing the unwinder. Note: The unwinder currently only works on Darwin and on ARM Linux. Non-ARM Linux support is not yet implemented, and will fail to build. llvm-svn: 212824
2014-07-11 23:36:02 +08:00
endif()
[libc++abi] Allow specifying custom Lit config files This is the libc++abi counterpart of 0c66af970c80.
2020-06-25 23:46:00 +08:00
set(AUTO_GEN_COMMENT "## Autogenerated by libcxxabi configuration.\n# Do not edit!")
[libc++] Serialize Lit parameters to make them available to from-scratch configs Before this patch, Lit parameters that were set as a result of CMake options were not made available to from-scratch configs. This patch serializes those parameters into the generated lit config file so that they are available to all configs. Differential Revision: https://reviews.llvm.org/D105047
2021-06-02 05:16:11 +08:00
set(SERIALIZED_LIT_PARAMS "# Lit parameters serialized here for llvm-lit to pick them up\n")
macro(serialize_lit_param param value)
string(APPEND SERIALIZED_LIT_PARAMS "config.${param} = ${value}\n")
endmacro()
if (NOT LIBCXXABI_ENABLE_EXCEPTIONS)
serialize_lit_param(enable_exceptions False)
endif()
[libc++][libc++abi] Serialize the enable_assertions Lit parameter in the generated config This means that re-running with llvm-lit in that configuration will work as expected. This also enables assertions in libc++abi in the Generic-assertions CI job, which was disabled previously. Differential Revision: https://reviews.llvm.org/D122597
2022-03-29 01:10:14 +08:00
if (LIBCXXABI_ENABLE_ASSERTIONS)
serialize_lit_param(enable_assertions True)
endif()
[libc++] Serialize Lit parameters to make them available to from-scratch configs Before this patch, Lit parameters that were set as a result of CMake options were not made available to from-scratch configs. This patch serializes those parameters into the generated lit config file so that they are available to all configs. Differential Revision: https://reviews.llvm.org/D105047
2021-06-02 05:16:11 +08:00
serialize_lit_param(enable_experimental False)
if (LLVM_USE_SANITIZER)
serialize_lit_param(use_sanitizer "\"${LLVM_USE_SANITIZER}\"")
endif()
[runtimes] Remove FOO_TARGET_TRIPLE, FOO_SYSROOT and FOO_GCC_TOOLCHAIN Instead, folks can use the equivalent variables provided by CMake to set those. This removal aims to reduce complexity and potential for confusion when setting the target triple for building the runtimes, and make it correct when `CMAKE_OSX_ARCHITECTURES` is used (right now both `-arch` and `--target=` will end up being passed, which is downright incorrect). Differential Revision: https://reviews.llvm.org/D112155
2021-10-13 03:59:08 +08:00
if (CMAKE_CXX_COMPILER_TARGET)
serialize_lit_param(target_triple "\"${CMAKE_CXX_COMPILER_TARGET}\"")
else()
serialize_lit_param(target_triple "\"${LLVM_DEFAULT_TARGET_TRIPLE}\"")
[libc++] Serialize Lit parameters to make them available to from-scratch configs Before this patch, Lit parameters that were set as a result of CMake options were not made available to from-scratch configs. This patch serializes those parameters into the generated lit config file so that they are available to all configs. Differential Revision: https://reviews.llvm.org/D105047
2021-06-02 05:16:11 +08:00
endif()
[runtimes] Serialize all Lit params instead of passing them to add_lit_testsuite add_lit_testsuite() takes Lit parameters passed to it and adds them to the parameters used globally when running all test suites. That means that a target like `check-all`, which ends up calling Lit on the whole monorepo, will see the test parameters for all the individual project's test suites. So, for example, it would see `--param std=c++03` (from libc++abi), and `--param std=c++03` (from libc++), and `--param whatever` (from another project being tested at the same time). While always unclean, that works when the parameters all agree. However, if the parameters share the same name but have different values, only one of those two values will be used and it will be incredibly confusing to understand why one of the test suites is being run with the incorrect parameter value. For that reason, this commit moves away from using add_lit_testsuite()'s PARAM functionality, and serializes the parameter values for the runtimes in the generated config.py file instead, which is local to the specific test suite. Differential Revision: https://reviews.llvm.org/D105991
2021-07-14 23:36:22 +08:00
foreach(param IN LISTS LIBCXXABI_TEST_PARAMS)
string(REGEX REPLACE "(.+)=(.+)" "\\1" name "${param}")
string(REGEX REPLACE "(.+)=(.+)" "\\2" value "${param}")
serialize_lit_param("${name}" "\"${value}\"")
endforeach()
[libc++abi][ci] Add a from-scratch config for libc++abi on Apple/system I came across an issue where since we build the library for Apple with the install name directory being /usr/lib, which means that if we don't run the tests with DYLD_LIBRARY_PATH, we'll end up loading the system-provided libc++abi when running the tests. That wreaks havoc. Instead of fixing it in the legacy config file, this commit introduces an Apple libc++abi config file that does the right thing. Differential Revision: https://reviews.llvm.org/D111279
2021-10-13 05:45:45 +08:00
configure_file("${CMAKE_CURRENT_SOURCE_DIR}/configs/cmake-bridge.cfg.in"
"${CMAKE_CURRENT_BINARY_DIR}/cmake-bridge.cfg"
@ONLY)
Fix standalone test-suite run. This patch updates libc++abi's HandleOutOfTreeLLVM.cmake to match libc++'s -- and more importantly, to fix a bug where llvm-lit wasn't found/created when libc++abi was built out-of-tree. This prevented the test suite from running. llvm-svn: 322768
2018-01-18 06:07:09 +08:00
configure_lit_site_cfg(
[libc++abi] Allow specifying custom Lit config files This is the libc++abi counterpart of 0c66af970c80.
2020-06-25 23:46:00 +08:00
"${LIBCXXABI_TEST_CONFIG}"
${CMAKE_CURRENT_BINARY_DIR}/lit.site.cfg
MAIN_CONFIG "${CMAKE_CURRENT_SOURCE_DIR}/lit.cfg.py")
Fix standalone test-suite run. This patch updates libc++abi's HandleOutOfTreeLLVM.cmake to match libc++'s -- and more importantly, to fix a bug where llvm-lit wasn't found/created when libc++abi was built out-of-tree. This prevented the test suite from running. llvm-svn: 322768
2018-01-18 06:07:09 +08:00
[runtimes] Use add_lit_testsuite to register lit testsuites The runtimes build uses variables set by add_lit_testsuite to collect testsuites from all the runtimes. Differential Revision: https://reviews.llvm.org/D97913
2021-03-04 14:40:11 +08:00
add_lit_testsuite(check-cxxabi "Running libcxxabi tests"
Add lit configs for libcxxabi tests. This makes running libcxxabi tests on Linux _much_ easier. Adds a check-libcxxabi target to cmake. Also defaults to building a dynamic libc++abi. This is so that the default options still test the libc++abi that is being built. There are two problems with testing a static libc++abi. In the case of a standalone build, the tests will link the system's libc++, which might not have been built against our libc++abi. In the case of an in tree build, libc++ will prefer a dynamic libc++abi from the system over a static libc++abi from the output directory. llvm-svn: 212672
2014-07-10 10:20:11 +08:00
${CMAKE_CURRENT_BINARY_DIR}
[runtimes] Serialize all Lit params instead of passing them to add_lit_testsuite add_lit_testsuite() takes Lit parameters passed to it and adds them to the parameters used globally when running all test suites. That means that a target like `check-all`, which ends up calling Lit on the whole monorepo, will see the test parameters for all the individual project's test suites. So, for example, it would see `--param std=c++03` (from libc++abi), and `--param std=c++03` (from libc++), and `--param whatever` (from another project being tested at the same time). While always unclean, that works when the parameters all agree. However, if the parameters share the same name but have different values, only one of those two values will be used and it will be incredibly confusing to understand why one of the test suites is being run with the incorrect parameter value. For that reason, this commit moves away from using add_lit_testsuite()'s PARAM functionality, and serializes the parameter values for the runtimes in the generated config.py file instead, which is local to the specific test suite. Differential Revision: https://reviews.llvm.org/D105991
2021-07-14 23:36:22 +08:00
DEPENDS ${LIBCXXABI_TEST_DEPS})