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

144 lines
3.5 KiB
CMake
Raw Normal View History

Switch Clang to use the new common LLVM CMake infrastructure for adding lit testsuites. This sinks all management of the aggregate lit runs into the LLVM CMake files, making Clang only responsible for declaring its own testsuite. In the process we fix numerous "bugs" where the proper method of invoking lit has changed over time, and the old system encoded several broken artifacts of this in ABIs and compatibility tests. It also switches to 'check-clang' for the canonical name of the test suite, although 'clang-test' remains as an alias. The situation when Clang is being built in standalone mode is little changed. It replicates just enough of the lit setup to cope with the oddities of being run outside of an LLVM build. llvm-svn: 159483
2012-06-30 18:14:27 +08:00
# Test runner infrastructure for Clang. This configures the Clang test trees
# for use by Lit, and delegates to LLVM's lit test handlers.
First cut at regression testing Clang with CMake llvm-svn: 72945
2009-06-06 00:00:31 +08:00
[CMake][Standalone] Fixup r197395 for standalone build. Standalone scripts shall be rewritten. llvm-svn: 197459
2013-12-17 12:14:17 +08:00
if (CMAKE_CFG_INTDIR STREQUAL ".")
set(LLVM_BUILD_MODE ".")
else ()
set(LLVM_BUILD_MODE "%(build_mode)s")
endif ()
[CMake] Deprecate CLANG_RUNTIME_OUTPUT_INTDIR and CLANG_LIBRARY_OUTPUT_INTDIR. LLVM_*_OUTPUT_INTDIR should be available everywhere. It was my mistake when I introduced INTDIR stuff. llvm-svn: 199597
2014-01-19 21:00:01 +08:00
string(REPLACE ${CMAKE_CFG_INTDIR} ${LLVM_BUILD_MODE} CLANG_TOOLS_DIR ${LLVM_RUNTIME_OUTPUT_INTDIR})
[CMake][Standalone] Fixup r197395 for standalone build. Standalone scripts shall be rewritten. llvm-svn: 197459
2013-12-17 12:14:17 +08:00
[test] Fix detecting LLVM zlib support in stand-alone builds Fix the test run to declare missing HAVE_LIBZ value in stand-alone builds, using the LLVM_ENABLE_ZLIB that is exported in LLVMConfig.cmake. When using in-tree builds, HAVE_LIBZ is declared in cmake/config-ix.cmake as a result of LLVM's CMake checks. When building stand-alone, this value is not available and as a result caused clang to wrongly assume that LLVM was built without zlib support. To fix it, set it to the value of LLVM_ENABLE_ZLIB. While this variable is originally used to control the user preference, LLVM updates its value to 0 if zlib checks fail. Therefore, we can use it to reliably determine whether LLVM was built with zlib support or not. Differential Revision: https://reviews.llvm.org/D24869 llvm-svn: 285741
2016-11-02 04:31:52 +08:00
if(CLANG_BUILT_STANDALONE)
# Set HAVE_LIBZ according to recorded LLVM_ENABLE_ZLIB value. This
# value is forced to 0 if zlib was not found, so it is fine to use it
# instead of HAVE_LIBZ (not recorded).
if(LLVM_ENABLE_ZLIB)
set(HAVE_LIBZ 1)
endif()
endif()
[test] Port clang tests to canonicalized booleans Use the new llvm_canonicalize_cmake_booleans() function to canonicalize booleans for lit tests. Replace the duplicate ENABLE_CLANG* variables used to hold canonicalized values with in-place canonicalization. Use implicit logic in Python code to avoid overrelying on exact 0/1 values. Differential Revision: https://reviews.llvm.org/D28529 llvm-svn: 293052
2017-01-25 21:11:45 +08:00
llvm_canonicalize_cmake_booleans(
CLANG_BUILD_EXAMPLES
CLANG_ENABLE_ARCMT
CLANG_ENABLE_STATIC_ANALYZER
[test] Add HAVE_LIBZ to canonicalized booleans Canonicalize HAVE_LIBZ as well to fix buildbot failures. llvm-svn: 293053
2017-01-25 21:31:53 +08:00
ENABLE_BACKTRACES
HAVE_LIBZ)
[test] Port clang tests to canonicalized booleans Use the new llvm_canonicalize_cmake_booleans() function to canonicalize booleans for lit tests. Replace the duplicate ENABLE_CLANG* variables used to hold canonicalized values with in-place canonicalization. Use implicit logic in Python code to avoid overrelying on exact 0/1 values. Differential Revision: https://reviews.llvm.org/D28529 llvm-svn: 293052
2017-01-25 21:11:45 +08:00
Switch Clang's CMake lit.site.cfg generation over to use the common helpers rather than its own special-rolled code. llvm-svn: 159398
2012-06-29 08:39:23 +08:00
configure_lit_site_cfg(
[lit] Rename lld and clang lit configs to end in .py This follows in line with a previous patch of renaming LLVM's. Working on these files is difficult in certain operating systems and/or environments that don't like handling python code with a non .py file extension. llvm-svn: 313892
2017-09-22 01:38:13 +08:00
${CMAKE_CURRENT_SOURCE_DIR}/lit.site.cfg.py.in
${CMAKE_CURRENT_BINARY_DIR}/lit.site.cfg.py
MAIN_CONFIG
${CMAKE_CURRENT_SOURCE_DIR}/lit.cfg.py
Switch Clang's CMake lit.site.cfg generation over to use the common helpers rather than its own special-rolled code. llvm-svn: 159398
2012-06-29 08:39:23 +08:00
)
Rework site config for cmake to be generated at configure time, and only pass the 'build_config' value in at runtime using the new lit runtime user parameter feature. This simplifies things and drops a dependency on 'sed', FWIW. llvm-svn: 86421
2009-11-08 07:53:32 +08:00
Switch Clang's CMake lit.site.cfg generation over to use the common helpers rather than its own special-rolled code. llvm-svn: 159398
2012-06-29 08:39:23 +08:00
configure_lit_site_cfg(
[lit] Rename lld and clang lit configs to end in .py This follows in line with a previous patch of renaming LLVM's. Working on these files is difficult in certain operating systems and/or environments that don't like handling python code with a non .py file extension. llvm-svn: 313892
2017-09-22 01:38:13 +08:00
${CMAKE_CURRENT_SOURCE_DIR}/Unit/lit.site.cfg.py.in
${CMAKE_CURRENT_BINARY_DIR}/Unit/lit.site.cfg.py
MAIN_CONFIG
${CMAKE_CURRENT_SOURCE_DIR}/Unit/lit.cfg.py
Switch Clang's CMake lit.site.cfg generation over to use the common helpers rather than its own special-rolled code. llvm-svn: 159398
2012-06-29 08:39:23 +08:00
)
CMake: Fix test. CMake has not built unittests yet. llvm-svn: 124787
2011-02-03 17:01:12 +08:00
Switch Clang to use the new common LLVM CMake infrastructure for adding lit testsuites. This sinks all management of the aggregate lit runs into the LLVM CMake files, making Clang only responsible for declaring its own testsuite. In the process we fix numerous "bugs" where the proper method of invoking lit has changed over time, and the old system encoded several broken artifacts of this in ABIs and compatibility tests. It also switches to 'check-clang' for the canonical name of the test suite, although 'clang-test' remains as an alias. The situation when Clang is being built in standalone mode is little changed. It replicates just enough of the lit setup to cope with the oddities of being run outside of an LLVM build. llvm-svn: 159483
2012-06-30 18:14:27 +08:00
option(CLANG_TEST_USE_VG "Run Clang tests under Valgrind" OFF)
if(CLANG_TEST_USE_VG)
set(CLANG_TEST_EXTRA_ARGS ${CLANG_TEST_EXTRA_ARGS} "--vg")
endif ()
First cut at regression testing Clang with CMake llvm-svn: 72945
2009-06-06 00:00:31 +08:00
[CMake] check-clang: Append items to CLANG_TEST_DEPS rather than set. CLANG_TEST_DEPS can be set in parent scope. llvm-svn: 197687
2013-12-20 00:05:39 +08:00
list(APPEND CLANG_TEST_DEPS
CMake: Include Clang unit tests in check-clang target in standalone builds. Also, remove CLANG_BUILD_TESTS option. It won't have consistent behavior between standalone and non-standalone builds, so I'm not going to bother hooking it up for standalone builds. LLVM_BUILD_TESTS will continue to control unit test inclusion in the "all" target in non-standalone builds. Finally, fix the default value of CLANG_INCLUDE_TESTS, which was being set to the boolean value of "LLVM_INCLUDE_TESTS", i.e. OFF, rather than actually reading the variable ${LLVM_INCLUDE_TESTS}! If you picked up my earlier commit, YOU WILL HAVE TO MANUALLY SET THIS OPTION BACK ON. My apologies! Part two of r174691 (allow the unit tests to be built in standalone mode). llvm-svn: 174698
2013-02-08 15:28:25 +08:00
clang clang-headers
Fix the CLANG_ENABLE_STATIC_ANALYZER=OFF build. tools/clang/tools/CMakeLists.txt does not create the clang-check target when CLANG_ENABLE_STATIC_ANALYZER=OFF. llvm-svn: 271392
2016-06-01 21:47:26 +08:00
clang-format
Fix the !CLANG_ENABLE_ARCMT build llvm-svn: 212995
2014-07-15 06:17:16 +08:00
c-index-test diagtool
[CMake] check-clang requires clang-tblgen. It is not required by anyone when external CLANG_TABLEGEN is specified. llvm-svn: 199579
2014-01-19 16:54:48 +08:00
clang-tblgen
clang-offload-bundler - offload files bundling/unbundling tool Summary: One of the goals of programming models that support offloading (e.g. OpenMP) is to enable users to offload with little effort, by annotating the code with a few pragmas. I'd also like to save users the trouble of changing their existent applications' build system. So having the compiler always return a single file instead of one for the host and each target even if the user is doing separate compilation is desirable. This diff proposes a tool named clang-offload-bundler (happy to change the name if required) that is used to bundle files associated with the same user source file but different targets, or to unbundle a file into separate files associated with different targets. This tool supports the driver support for OpenMP under review in http://reviews.llvm.org/D9888. The tool is used there to enable separate compilation, so that the very first action on input files that are not source files is a "unbundling action" and the very last non-linking action is a "bundling action". The format of the bundled files is currently very simple: text formats are concatenated with comments that have a magic string and target identifying triple in between, and binary formats have a header that contains the triple and the offset and size of the code for host and each target. The goal is to improve this tool in the future to deal with archive files so that each individual file in the archive is properly dealt with. We see that archives are very commonly used in current applications to combine separate compilation results. So I'm convinced users would enjoy this feature. This tool can be used like this: `clang-offload-bundler -targets=triple1,triple2 -type=ii -inputs=a.triple1.ii,a.triple2.ii -outputs=a.ii` or `clang-offload-bundler -targets=triple1,triple2 -type=ii -outputs=a.triple1.ii,a.triple2.ii -inputs=a.ii -unbundle` I implemented the tool under clang/tools. Please let me know if something like this should live somewhere else. This patch is prerequisite for http://reviews.llvm.org/D9888. Reviewers: hfinkel, rsmith, echristo, chandlerc, tra, jlebar, ABataev, Hahnfeld Subscribers: whchung, caomhin, andreybokhanko, arpith-jacob, carlo.bertolli, mehdi_amini, guansong, Hahnfeld, cfe-commits Differential Revision: https://reviews.llvm.org/D13909 llvm-svn: 279632
2016-08-24 23:21:05 +08:00
clang-offload-bundler
Testbed and skeleton of a new expression parser Recommitted after formal approval. LLVM's JIT is now the foundation of dynamic-compilation features for many languages. Clang also has low-level support for dynamic compilation (ASTImporter and ExternalASTSource, notably). How the compiler is set up for dynamic parsing is generally left up to individual clients, for example LLDB's C/C++/Objective-C expression parser and the ROOT project. Although this arrangement offers external clients the flexibility to implement dynamic features as they see fit, the lack of an in-tree client means that subtle bugs can be introduced that cause regressions in the external clients but aren't caught by tests (or users) until much later. LLDB for example regularly encounters complicated ODR violation scenarios where it is not immediately clear who is at fault. Other external clients (notably, Cling) rely on similar functionality, and another goal is to break this functionality up into composable parts so that any client can be built easily on top of Clang without requiring extensive additional code. I propose that the parts required to build a simple expression parser be added to Clang. Initially, I aim to have the following features: A piece that looks up external declarations from a variety of sources (e.g., from previous dynamic compilations, from modules, or from DWARF) and uses clear conflict resolution rules to reconcile differences, with easily understood errors. This functionality will be supported by in-tree tests. A piece that works hand in hand with the LLVM JIT to resolve the locations of external declarations so that e.g. variables can be redeclared and (for high-performance applications like DTrace) external variables can be accessed directly from the registers where they reside. This commit adds a tester that parses a sequence of source files and then uses them as source data for an expression. External references are resolved using an ExternalASTSource that responds to name queries using an ASTImporter. This is the setup that LLDB uses, and the motivating reason for MinimalImport in ASTImporter. When complete, this tester will implement the first of the above goals. Differential Revision: https://reviews.llvm.org/D27180 llvm-svn: 290367
2016-12-23 04:03:14 +08:00
clang-import-test
[refactor] Move clang-rename into the clang repository The core engine of clang-rename will be used for local and global renames in the new refactoring engine, as mentioned in http://lists.llvm.org/pipermail/cfe-dev/2017-June/054286.html. The clang-rename tool is still supported but might get deprecated in the future. Differential Revision: https://reviews.llvm.org/D34696 llvm-svn: 306840
2017-07-01 00:36:09 +08:00
clang-rename
[refactor] add clang-refactor tool with initial testing support and local-rename action This commit introduces the clang-refactor tool alongside the local-rename action which uses the existing renaming engine used by clang-rename. The tool doesn't actually perform the source transformations yet, it just provides testing support. This commit also moves only one test from clang-rename over to test/Refactor. I will continue to move the other tests throughout development of clang-refactor. The following options are supported by clang-refactor: -v: use verbose output -selection: The source range that corresponds to the portion of the source that's selected (currently only special command test:<file> is supported). Please note that a follow-up commit will migrate clang-refactor to libTooling's common option parser, so clang-refactor will be able to use the common interface with compilation database and options like -p, -extra-arg, etc. The testing support provided by clang-refactor is described below: When -selection=test:<file> is given, clang-refactor will parse the selection commands from that file. The selection commands are grouped and the specified refactoring action invoked by the tool. Each command in a group is expected to produce an identical result. The precise syntax for the selection commands is described in a comment in TestSupport.h. Differential Revision: https://reviews.llvm.org/D36574 llvm-svn: 313244
2017-09-14 18:06:52 +08:00
clang-refactor
Clang's tests should depend on clang-diff llvm-svn: 308735
2017-07-21 21:12:01 +08:00
clang-diff
CMake: Include Clang unit tests in check-clang target in standalone builds. Also, remove CLANG_BUILD_TESTS option. It won't have consistent behavior between standalone and non-standalone builds, so I'm not going to bother hooking it up for standalone builds. LLVM_BUILD_TESTS will continue to control unit test inclusion in the "all" target in non-standalone builds. Finally, fix the default value of CLANG_INCLUDE_TESTS, which was being set to the boolean value of "LLVM_INCLUDE_TESTS", i.e. OFF, rather than actually reading the variable ${LLVM_INCLUDE_TESTS}! If you picked up my earlier commit, YOU WILL HAVE TO MANUALLY SET THIS OPTION BACK ON. My apologies! Part two of r174691 (allow the unit tests to be built in standalone mode). llvm-svn: 174698
2013-02-08 15:28:25 +08:00
)
Fix the CLANG_ENABLE_STATIC_ANALYZER=OFF build. tools/clang/tools/CMakeLists.txt does not create the clang-check target when CLANG_ENABLE_STATIC_ANALYZER=OFF. llvm-svn: 271392
2016-06-01 21:47:26 +08:00
if(CLANG_ENABLE_STATIC_ANALYZER)
list(APPEND CLANG_TEST_DEPS
clang-check
[test] Enable clang-func-mapping as a test dep with the analyzer clang-func-mapping should not be a test dependency when the static analyzer isn't being built. llvm-svn: 314036
2017-09-23 06:17:10 +08:00
clang-func-mapping
Fix the CLANG_ENABLE_STATIC_ANALYZER=OFF build. tools/clang/tools/CMakeLists.txt does not create the clang-check target when CLANG_ENABLE_STATIC_ANALYZER=OFF. llvm-svn: 271392
2016-06-01 21:47:26 +08:00
)
endif()
Don't add examples to the check-clang dependencies unless requested The tests were correctly getting skipped but the targets still mistakenly got built. llvm-svn: 209983
2014-06-01 10:02:23 +08:00
Fix the !CLANG_ENABLE_ARCMT build llvm-svn: 212995
2014-07-15 06:17:16 +08:00
if (CLANG_ENABLE_ARCMT)
list(APPEND CLANG_TEST_DEPS
arcmt-test
c-arcmt-test
)
endif ()
[test] Port clang tests to canonicalized booleans Use the new llvm_canonicalize_cmake_booleans() function to canonicalize booleans for lit tests. Replace the duplicate ENABLE_CLANG* variables used to hold canonicalized values with in-place canonicalization. Use implicit logic in Python code to avoid overrelying on exact 0/1 values. Differential Revision: https://reviews.llvm.org/D28529 llvm-svn: 293052
2017-01-25 21:11:45 +08:00
if (CLANG_BUILD_EXAMPLES)
Don't add examples to the check-clang dependencies unless requested The tests were correctly getting skipped but the targets still mistakenly got built. llvm-svn: 209983
2014-06-01 10:02:23 +08:00
list(APPEND CLANG_TEST_DEPS
clang/test/Frontend/plugin-annotate-functions.c requires the target examples/AnnotateFunctions. llvm-svn: 263931
2016-03-21 19:03:39 +08:00
AnnotateFunctions
Don't add examples to the check-clang dependencies unless requested The tests were correctly getting skipped but the targets still mistakenly got built. llvm-svn: 209983
2014-06-01 10:02:23 +08:00
clang-interpreter
PrintFunctionNames
Fix build with various feature flag combinations llvm-svn: 212996
2014-07-15 06:17:22 +08:00
)
endif ()
[test] Port clang tests to canonicalized booleans Use the new llvm_canonicalize_cmake_booleans() function to canonicalize booleans for lit tests. Replace the duplicate ENABLE_CLANG* variables used to hold canonicalized values with in-place canonicalization. Use implicit logic in Python code to avoid overrelying on exact 0/1 values. Differential Revision: https://reviews.llvm.org/D28529 llvm-svn: 293052
2017-01-25 21:11:45 +08:00
if (CLANG_ENABLE_STATIC_ANALYZER AND CLANG_BUILD_EXAMPLES)
Fix build with various feature flag combinations llvm-svn: 212996
2014-07-15 06:17:22 +08:00
list(APPEND CLANG_TEST_DEPS
Don't add examples to the check-clang dependencies unless requested The tests were correctly getting skipped but the targets still mistakenly got built. llvm-svn: 209983
2014-06-01 10:02:23 +08:00
SampleAnalyzerPlugin
)
endif ()
CMake: Include Clang unit tests in check-clang target in standalone builds. Also, remove CLANG_BUILD_TESTS option. It won't have consistent behavior between standalone and non-standalone builds, so I'm not going to bother hooking it up for standalone builds. LLVM_BUILD_TESTS will continue to control unit test inclusion in the "all" target in non-standalone builds. Finally, fix the default value of CLANG_INCLUDE_TESTS, which was being set to the boolean value of "LLVM_INCLUDE_TESTS", i.e. OFF, rather than actually reading the variable ${LLVM_INCLUDE_TESTS}! If you picked up my earlier commit, YOU WILL HAVE TO MANUALLY SET THIS OPTION BACK ON. My apologies! Part two of r174691 (allow the unit tests to be built in standalone mode). llvm-svn: 174698
2013-02-08 15:28:25 +08:00
set(CLANG_TEST_PARAMS
clang_site_config=${CMAKE_CURRENT_BINARY_DIR}/lit.site.cfg
)
CMake: Add support for running tests with valgrind. llvm-svn: 89625
2009-11-23 05:55:22 +08:00
CMake: Include Clang unit tests in check-clang target in standalone builds. Also, remove CLANG_BUILD_TESTS option. It won't have consistent behavior between standalone and non-standalone builds, so I'm not going to bother hooking it up for standalone builds. LLVM_BUILD_TESTS will continue to control unit test inclusion in the "all" target in non-standalone builds. Finally, fix the default value of CLANG_INCLUDE_TESTS, which was being set to the boolean value of "LLVM_INCLUDE_TESTS", i.e. OFF, rather than actually reading the variable ${LLVM_INCLUDE_TESTS}! If you picked up my earlier commit, YOU WILL HAVE TO MANUALLY SET THIS OPTION BACK ON. My apologies! Part two of r174691 (allow the unit tests to be built in standalone mode). llvm-svn: 174698
2013-02-08 15:28:25 +08:00
if( NOT CLANG_BUILT_STANDALONE )
list(APPEND CLANG_TEST_DEPS
check-clang: Introduce get_llvm_config_props in clang/test/lit.cfg. In trunk, we can use features as below: aarch64-registered-target hexagon-registered-target msp430-registered-target r600-registered-target systemz-registered-target xcore-registered-target Each of them, as below, implies corresponding subtargets: arm-registered-target -- arm, thumb mips-registered-target -- mips, mips64, mips64el, mipsel nvptx-registered-target -- nvptx, nvptx64 sparc-registered-target -- sparc, sparcv9 x86-registered-target -- x86, x86-64 They will be renamed: cppbackend-registered-target -- was "cpp". Unused in trunk. powerpc-registered-target -- was "ppc32", "ppc64" and "ppc64le". The feature "asserts" is also taken from llvm-config. llvm-svn: 196347
2013-12-04 11:40:56 +08:00
llvm-config
[CMake] Reformat CLANG_TEST_DEPS. llvm-svn: 247553
2015-09-14 20:41:53 +08:00
FileCheck count not
[CMake] Reformat CLANG_TEST_DEPS. llvm-svn: 250503
2015-10-16 17:38:42 +08:00
llc
llvm-bcanalyzer
IRGen: When loading the main module in the distributed ThinLTO backend, look for the module containing the summary. Differential Revision: https://reviews.llvm.org/D29067 llvm-svn: 293209
2017-01-27 05:09:48 +08:00
llvm-cat
Add llvm-dis dependency to check-clang. llvm-svn: 292450
2017-01-19 08:04:44 +08:00
llvm-dis
[ThinLTO/CFI] Include TYPE_ID summaries into GLOBALVAL_SUMMARY_BLOCK Summary: TypeID summaries are used by CFI and need to be serialized by ThinLTO indexing for later use by LTO Backend. Reviewers: tejohnson, pcc Subscribers: mehdi_amini, inglorion, eraman, hiraditya, llvm-commits Differential Revision: https://reviews.llvm.org/D42611 llvm-svn: 325182
2018-02-15 06:41:15 +08:00
llvm-lto2
Re-apply r292662, "IRGen: Start using the WriteThinLTOBitcode pass." The internal build issue has been resolved. llvm-svn: 293231
2017-01-27 07:51:50 +08:00
llvm-modextract
Add missing test dependency. llvm-svn: 273351
2016-06-22 09:03:15 +08:00
llvm-nm
[CMake] Reformat CLANG_TEST_DEPS. llvm-svn: 250503
2015-10-16 17:38:42 +08:00
llvm-objdump
llvm-profdata
llvm-readobj
llvm-symbolizer
opt
We support a mode where the Clang regression tests are run but not the Clang unit tests. It's not clear why we support this mode in builds where LLVM is available (LLVM itself does not), but at least this makes us support it correctly. This also fixes a long-standing bug where we would pass the unit test param flag to lit in the standalone build even though the standalone build *never* has the unittests built and ready for testing. llvm-svn: 159594
2012-07-03 05:37:04 +08:00
)
[cmake] Fix builds with LLVM_ENABLE_PIC=0 Summary: When this flag is specified, the target llvm-lto is not built, but is still used as a dependency of the test targets. cmake 2.8 silently ignored this situation, but with cmake_minimum_required(3.4) it becomes an error. Fix this by avoiding the inclusion the target as a dependency. Reviewers: beanz Subscribers: cfe-commits Differential Revision: http://reviews.llvm.org/D20883 llvm-svn: 271533
2016-06-03 00:35:24 +08:00
if(TARGET llvm-lto)
[cmake] Fix-up r271533 I was appending to the wrong variable (over-zealous copy-paste from llvm on my part). llvm-svn: 271565
2016-06-03 02:49:42 +08:00
list(APPEND CLANG_TEST_DEPS llvm-lto)
[cmake] Fix builds with LLVM_ENABLE_PIC=0 Summary: When this flag is specified, the target llvm-lto is not built, but is still used as a dependency of the test targets. cmake 2.8 silently ignored this situation, but with cmake_minimum_required(3.4) it becomes an error. Fix this by avoiding the inclusion the target as a dependency. Reviewers: beanz Subscribers: cfe-commits Differential Revision: http://reviews.llvm.org/D20883 llvm-svn: 271533
2016-06-03 00:35:24 +08:00
endif()
Add target_triple to Clang site configuration. llvm-svn: 85881
2009-11-03 15:25:53 +08:00
endif()
Switch Clang to use the new common LLVM CMake infrastructure for adding lit testsuites. This sinks all management of the aggregate lit runs into the LLVM CMake files, making Clang only responsible for declaring its own testsuite. In the process we fix numerous "bugs" where the proper method of invoking lit has changed over time, and the old system encoded several broken artifacts of this in ABIs and compatibility tests. It also switches to 'check-clang' for the canonical name of the test suite, although 'clang-test' remains as an alias. The situation when Clang is being built in standalone mode is little changed. It replicates just enough of the lit setup to cope with the oddities of being run outside of an LLVM build. llvm-svn: 159483
2012-06-30 18:14:27 +08:00
[CMake] Add convenience target clang-test-depends to build test dependencies. This is useful when paired with the distribution targets to build prerequisites for running tests. llvm-svn: 262429
2016-03-02 08:27:15 +08:00
add_custom_target(clang-test-depends DEPENDS ${CLANG_TEST_DEPS})
Moving clang-test-depends into the Clang tests folder and moving vtables_blacklist into the Misc folder; NFC, this simply cleans up the generated solution so that these targets don't live in the root folder of the IDE. llvm-svn: 266079
2016-04-12 23:09:17 +08:00
set_target_properties(clang-test-depends PROPERTIES FOLDER "Clang tests")
[CMake] Add convenience target clang-test-depends to build test dependencies. This is useful when paired with the distribution targets to build prerequisites for running tests. llvm-svn: 262429
2016-03-02 08:27:15 +08:00
[CMake][Standalone] Rewrite standalone build based on llvm-config. CLANG_PATH_TO_LLVM_*(s) are deprecated. Checked on VS10(multiconfig) and some singleconfig builders. * Assumptions - You should specify llvm-config as LLVM_CONFIG. CMake could find one in $PATH by default. - ENABLE_ASSERTIONS obeys LLVM's. * Use cases a) With LLVM build tree Assume llvm-config is in your build tree. Everything should work as ever. b) With *installed* LLVM Assume distributions. The source tree can be optional. b1) The source tree is provided on the location `llvm-config --src-root` - Test utils, FileCheck &c., are imported and built in the new tree. - Gtest is built in the tree if gtest library is not found. - Lit is used in $(SRCROOT)/utils/lit/lit.py. b2) The source tree is not provided - clang and utilities can be built. - All tests, unittests and check-clang are invalidated and not built. llvm-svn: 197697
2013-12-20 00:44:32 +08:00
add_lit_testsuite(check-clang "Running the Clang regression tests"
${CMAKE_CURRENT_BINARY_DIR}
check-clang: Suppress LLVM_LIT in add_lit_testsuite, for now. llvm-svn: 197702
2013-12-20 01:10:30 +08:00
#LIT ${LLVM_LIT}
[CMake][Standalone] Rewrite standalone build based on llvm-config. CLANG_PATH_TO_LLVM_*(s) are deprecated. Checked on VS10(multiconfig) and some singleconfig builders. * Assumptions - You should specify llvm-config as LLVM_CONFIG. CMake could find one in $PATH by default. - ENABLE_ASSERTIONS obeys LLVM's. * Use cases a) With LLVM build tree Assume llvm-config is in your build tree. Everything should work as ever. b) With *installed* LLVM Assume distributions. The source tree can be optional. b1) The source tree is provided on the location `llvm-config --src-root` - Test utils, FileCheck &c., are imported and built in the new tree. - Gtest is built in the tree if gtest library is not found. - Lit is used in $(SRCROOT)/utils/lit/lit.py. b2) The source tree is not provided - clang and utilities can be built. - All tests, unittests and check-clang are invalidated and not built. llvm-svn: 197697
2013-12-20 00:44:32 +08:00
PARAMS ${CLANG_TEST_PARAMS}
DEPENDS ${CLANG_TEST_DEPS}
ARGS ${CLANG_TEST_EXTRA_ARGS}
)
set_target_properties(check-clang PROPERTIES FOLDER "Clang tests")
Re-apply "test: Use add_lit_testsuites so that subsets of tests can be specified" This version should actually remove the empty directories I removed all of the files from. Thanks to tstellar for pointing out git-svn's --rmdir flag. Original message: This creates make/ninja targets like check-clang-codegen and check-clang-unit, much like LLVM already has. I had to move some input files into Input directories so they weren't picked up as test directories. llvm-svn: 274565
2016-07-06 01:54:40 +08:00
add_lit_testsuites(CLANG ${CMAKE_CURRENT_SOURCE_DIR}
PARAMS ${CLANG_TEST_PARAMS}
DEPENDS ${CLANG_TEST_DEPS}
)
Switch Clang to use the new common LLVM CMake infrastructure for adding lit testsuites. This sinks all management of the aggregate lit runs into the LLVM CMake files, making Clang only responsible for declaring its own testsuite. In the process we fix numerous "bugs" where the proper method of invoking lit has changed over time, and the old system encoded several broken artifacts of this in ABIs and compatibility tests. It also switches to 'check-clang' for the canonical name of the test suite, although 'clang-test' remains as an alias. The situation when Clang is being built in standalone mode is little changed. It replicates just enough of the lit setup to cope with the oddities of being run outside of an LLVM build. llvm-svn: 159483
2012-06-30 18:14:27 +08:00
# Add a legacy target spelling: clang-test
Extend a workaround for a CMake bug in LLVM's r159593 to apply to a Clang target which hits the same bug directly. llvm-svn: 159598
2012-07-03 05:46:03 +08:00
add_custom_target(clang-test)
add_dependencies(clang-test check-clang)
Switch Clang to use the new common LLVM CMake infrastructure for adding lit testsuites. This sinks all management of the aggregate lit runs into the LLVM CMake files, making Clang only responsible for declaring its own testsuite. In the process we fix numerous "bugs" where the proper method of invoking lit has changed over time, and the old system encoded several broken artifacts of this in ABIs and compatibility tests. It also switches to 'check-clang' for the canonical name of the test suite, although 'clang-test' remains as an alias. The situation when Clang is being built in standalone mode is little changed. It replicates just enough of the lit setup to cope with the oddities of being run outside of an LLVM build. llvm-svn: 159483
2012-06-30 18:14:27 +08:00
set_target_properties(clang-test PROPERTIES FOLDER "Clang tests")
[debuginfo-tests] Add support for moving debuginfo-tests from clang/test to llvm/projects or monorepo. Summary: The new version of debuginfo-tests will have it's own lit.cfg.py file which is incompatible with the one in clang/test. This change supports both the old and new versions, and can be used until the bots actually move debuginfo-tests to either clang/test or the monorepo. This is a prerequisite for D40971. Reviewers: zturner, aprantl Subscribers: mgorny, JDevlieghere, llvm-commits, cfe-commits Differential Revision: https://reviews.llvm.org/D41055 llvm-svn: 320494
2017-12-13 00:48:35 +08:00
# FIXME: This logic can be removed once all buildbots have moved
# debuginfo-test from clang/test to llvm/projects or monorepo.
[cmake] Follow-up to rL320494. EXISTS requires full paths. llvm-svn: 320519
2017-12-13 03:47:40 +08:00
if(EXISTS ${CMAKE_CURRENT_SOURCE_DIR}/debuginfo-tests)
[debuginfo-tests] Add support for moving debuginfo-tests from clang/test to llvm/projects or monorepo. Summary: The new version of debuginfo-tests will have it's own lit.cfg.py file which is incompatible with the one in clang/test. This change supports both the old and new versions, and can be used until the bots actually move debuginfo-tests to either clang/test or the monorepo. This is a prerequisite for D40971. Reviewers: zturner, aprantl Subscribers: mgorny, JDevlieghere, llvm-commits, cfe-commits Differential Revision: https://reviews.llvm.org/D41055 llvm-svn: 320494
2017-12-13 00:48:35 +08:00
message(WARNING "Including debuginfo-tests in clang/test is deprecated. Move to llvm/projects or use monorepo.")
[cmake] Follow-up to rL320494. EXISTS requires full paths. llvm-svn: 320519
2017-12-13 03:47:40 +08:00
if(EXISTS ${CMAKE_CURRENT_SOURCE_DIR}/debuginfo-tests/CMakeLists.txt)
[debuginfo-tests] Add support for moving debuginfo-tests from clang/test to llvm/projects or monorepo. Summary: The new version of debuginfo-tests will have it's own lit.cfg.py file which is incompatible with the one in clang/test. This change supports both the old and new versions, and can be used until the bots actually move debuginfo-tests to either clang/test or the monorepo. This is a prerequisite for D40971. Reviewers: zturner, aprantl Subscribers: mgorny, JDevlieghere, llvm-commits, cfe-commits Differential Revision: https://reviews.llvm.org/D41055 llvm-svn: 320494
2017-12-13 00:48:35 +08:00
add_subdirectory(debuginfo-tests)
endif()
endif()