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

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

186 lines
4.4 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
Revert "[CMake] Simplify CMake handling for zlib" This quietly disabled use of zlib on Windows even when building with -DLLVM_ENABLE_ZLIB=FORCE_ON. > Rather than handling zlib handling manually, use find_package from CMake > to find zlib properly. Use this to normalize the LLVM_ENABLE_ZLIB, > HAVE_ZLIB, HAVE_ZLIB_H. Furthermore, require zlib if LLVM_ENABLE_ZLIB is > set to YES, which requires the distributor to explicitly select whether > zlib is enabled or not. This simplifies the CMake handling and usage in > the rest of the tooling. > > This is a reland of abb0075 with all followup changes and fixes that > should address issues that were reported in PR44780. > > Differential Revision: https://reviews.llvm.org/D79219 This reverts commit 10b1b4a231a485f1711d576e6131f6755e008abe and follow-ups 64d99cc6abed78c00a2a7863b02ce54911a5264f and f9fec0447e12da9e8cf4b628f6d45f4941e7d182.
2020-08-05 18:14:07 +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
[Clang][Driver] Re-use the calling process instead of creating a new process for the cc1 invocation With this patch, the clang tool will now call the -cc1 invocation directly inside the same process. Previously, the -cc1 invocation was creating, and waiting for, a new process. This patch therefore reduces the number of created processes during a build, thus it reduces build times on platforms where process creation can be costly (Windows) and/or impacted by a antivirus. It also makes debugging a bit easier, as there's no need to attach to the secondary -cc1 process anymore, breakpoints will be hit inside the same process. Crashes or signaling inside the -cc1 invocation will have the same side-effect as before, and will be reported through the same means. This behavior can be controlled at compile-time through the CLANG_SPAWN_CC1 cmake flag, which defaults to OFF. Setting it to ON will revert to the previous behavior, where any -cc1 invocation will create/fork a secondary process. At run-time, it is also possible to tweak the CLANG_SPAWN_CC1 environment variable. Setting it and will override the compile-time setting. A value of 0 calls -cc1 inside the calling process; a value of 1 will create a secondary process, as before. Differential Revision: https://reviews.llvm.org/D69825
2020-01-13 23:40:04 +08:00
CLANG_SPAWN_CC1
[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
[clang][NewPM] Fixing remaining -O0 tests that are broken under new PM - CodeGen/flatten.c will fail under new PM becausec the new PM AlwaysInliner seems to intentionally inline functions but not call sites marked with alwaysinline (D23299) - Tests that check remarks happen to check them for the inliner which is not turned on at O0. These tests just check that remarks work, but we can make separate tests for the new PM with -O1 so we can turn on the inliner and check the remarks with minimal changes. Differential Revision: https://reviews.llvm.org/D62225 llvm-svn: 363846
2019-06-20 01:41:30 +08:00
ENABLE_EXPERIMENTAL_NEW_PASS_MANAGER
Revert "[CMake] Simplify CMake handling for zlib" This quietly disabled use of zlib on Windows even when building with -DLLVM_ENABLE_ZLIB=FORCE_ON. > Rather than handling zlib handling manually, use find_package from CMake > to find zlib properly. Use this to normalize the LLVM_ENABLE_ZLIB, > HAVE_ZLIB, HAVE_ZLIB_H. Furthermore, require zlib if LLVM_ENABLE_ZLIB is > set to YES, which requires the distributor to explicitly select whether > zlib is enabled or not. This simplifies the CMake handling and usage in > the rest of the tooling. > > This is a reland of abb0075 with all followup changes and fixes that > should address issues that were reported in PR44780. > > Differential Revision: https://reviews.llvm.org/D79219 This reverts commit 10b1b4a231a485f1711d576e6131f6755e008abe and follow-ups 64d99cc6abed78c00a2a7863b02ce54911a5264f and f9fec0447e12da9e8cf4b628f6d45f4941e7d182.
2020-08-05 18:14:07 +08:00
HAVE_LIBZ
[Analysis] Only run plugins tests if plugins are actually enabled When plugins aren't enabled, don't try to run plugins tests. Don't enable plugins unconditionally based on the platform, instead check if LLVM shared library is actually being built which may not be the case for every host configuration, even if the host itself supports plugins. This addresses test failures introduced by r360891/D59464. Differential Revision: https://reviews.llvm.org/D62050 llvm-svn: 360991
2019-05-17 14:07:37 +08:00
LLVM_ENABLE_PER_TARGET_RUNTIME_DIR
Improve behavior in the case of stack exhaustion. Summary: Clang performs various recursive operations (such as template instantiation), and may use non-trivial amounts of stack space in each recursive step (for instance, due to recursive AST walks). While we try to keep the stack space used by such steps to a minimum and we have explicit limits on the number of such steps we perform, it's impractical to guarantee that we won't blow out the stack on deeply recursive template instantiations on complex ASTs, even with only a moderately high instantiation depth limit. The user experience in these cases is generally terrible: we crash with no hint of what went wrong. Under this patch, we attempt to do better: * Detect when the stack is nearly exhausted, and produce a warning with a nice template instantiation backtrace, telling the user that we might run slowly or crash. * For cases where we're forced to trigger recursive template instantiation in arbitrarily-deeply-nested contexts, check whether we're nearly out of stack space and allocate a new stack (by spawning a new thread) after producing the warning. Reviewers: rnk, aaron.ballman Subscribers: mgorny, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D66361 llvm-svn: 369940
2019-08-27 02:18:07 +08:00
LLVM_ENABLE_PLUGINS
LLVM_ENABLE_THREADS)
[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
Reland "Make it possible for lit.site.cfg to contain relative paths, and use it for llvm and clang" The problem on Windows was that the \b in "..\bin" was interpreted as an escape sequence. Use r"" strings to prevent that. This reverts commit ab11b9eefa16661017c2c7b3b34c46b069f43fb7, with raw strings in the lit.site.cfg.py.in files. Differential Revision: https://reviews.llvm.org/D77184
2020-04-03 03:51:58 +08:00
PATHS
"LLVM_SOURCE_DIR"
"LLVM_BINARY_DIR"
"LLVM_TOOLS_DIR"
"LLVM_LIBS_DIR"
"SHLIBDIR"
"LLVM_LIT_TOOLS_DIR"
"CLANG_BINARY_DIR"
"CLANG_SOURCE_DIR"
"CLANG_TOOLS_DIR"
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
Reland "Make it possible for lit.site.cfg to contain relative paths, and use it for llvm and clang" The problem on Windows was that the \b in "..\bin" was interpreted as an escape sequence. Use r"" strings to prevent that. This reverts commit ab11b9eefa16661017c2c7b3b34c46b069f43fb7, with raw strings in the lit.site.cfg.py.in files. Differential Revision: https://reviews.llvm.org/D77184
2020-04-03 03:51:58 +08:00
PATHS
"LLVM_SOURCE_DIR"
"LLVM_BINARY_DIR"
"LLVM_TOOLS_DIR"
"LLVM_LIBS_DIR"
"CLANG_BINARY_DIR"
"SHLIBDIR"
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
Make check-clang depend on the clang-check binary always check-clang (the target that runs all clang tests) used to only depend on clang-check (a binary like clang-tidy, clang-refactor, etc) if the static analyzer is enabled. However, several lit tests call clang-check unconditionally, so always depend on it. Fixes a "could not find clang-check" lit warning in clean builds with the static analyzer disabled. Also sort the deps in the CMake file and put just one dep on each line. Differential Revision: https://reviews.llvm.org/D61324 llvm-svn: 359717
2019-05-02 03:34:00 +08:00
c-index-test
clang
clang-resource-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
[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
[clang-scan-deps] initial outline of the tool that runs preprocessor to find dependencies over a JSON compilation database This commit introduces an outline for the clang-scan-deps tool that will be used to implement fast dependency discovery phase using implicit modules for explicit module builds. The initial version of the tool works by computing non-modular header dependencies for files in the compilation database without any optimizations (i.e. without source minimization from r362459). The tool spawns a number of worker threads to run the clang compiler workers in parallel. The immediate goal for clang-scan-deps is to create a ClangScanDeps library which will be used to build up this tool to use the source minimization and caching multi-threaded filesystem to implement the optimized non-incremental dependency scanning phase for a non-modular build. This will allow us to do benchmarks and comparisons for performance that the minimization and caching give us Differential Revision: https://reviews.llvm.org/D60233 llvm-svn: 363204
2019-06-13 05:32:49 +08:00
clang-scan-deps
Make check-clang depend on the clang-check binary always check-clang (the target that runs all clang tests) used to only depend on clang-check (a binary like clang-tidy, clang-refactor, etc) if the static analyzer is enabled. However, several lit tests call clang-check unconditionally, so always depend on it. Fixes a "could not find clang-check" lit warning in clean builds with the static analyzer disabled. Also sort the deps in the CMake file and put just one dep on each line. Differential Revision: https://reviews.llvm.org/D61324 llvm-svn: 359717
2019-05-02 03:34:00 +08:00
diagtool
Re-apply: Add python tool to dump and construct header maps Header maps are binary files used by Xcode, which are used to map header names or paths to other locations. Clang has support for those since its inception, but there's not a lot of header map testing around. Since it's a binary format, testing becomes pretty much brittle and its hard to even know what's inside if you don't have the appropriate tools. Add a python based tool that allows creating and dumping header maps based on a json description of those. While here, rewrite tests to use the tool and remove the binary files from the tree. This tool was initially written by Daniel Dunbar. Thanks to Stella Stamenova for helping make this work on Windows. Differential Revision: https://reviews.llvm.org/D46485 rdar://problem/39994722 llvm-svn: 335295
2018-06-22 05:45:24 +08:00
hmaptool
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
Revert r359717, "Make check-clang depend on the clang-check binary always" The Tooling tests do have a lit.local.cfg with if not config.root.clang_staticanalyzer: config.unsupported = True so what's wrong isn't the missing dep, but that lit prints a warning for the binary missing. This will need a different kind of fix. llvm-svn: 359739
2019-05-02 07:32:38 +08:00
clang-check
[analyzer][CrossTU][NFC] Generalize to external definitions instead of external functions Summary: This is just changing naming and documentation to be general about external definitions that can be imported for cross translation unit analysis. There is at least a plan to add VarDecls: D46421 Reviewers: NoQ, xazax.hun, martong, a.sidorin, george.karpenkov, serge-sans-paille Reviewed By: xazax.hun, martong Subscribers: mgorny, whisperity, baloghadamsoftware, szepet, rnkovacs, mikhail.ramalho, Szelethus, donat.nagy, dkrupp, cfe-commits Differential Revision: https://reviews.llvm.org/D56441 llvm-svn: 350852
2019-01-11 01:44:04 +08:00
clang-extdef-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
Add an attribute plugin example Differential Revision: https://reviews.llvm.org/D31343
2020-03-25 21:49:02 +08:00
Attribute
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 ()
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
[analyzer] [NFC] Introduce separate targets for testing the analyzer: check-clang-analyzer and check-clang-analyzer-z3 Current testing setup for analyzer tests with Z3 is rather inconvenient: There's no way to run the analyzer tests separately (I use LIT_FILTER=Analysis ninja check-clang, but a direct target is nicer). When Clang is built with Z3 support, there's no way to *not* run tests with Z3 solver, and this is often desired, as tests with Z3 solver take a very long time. This patch introduces two extra targets: - check-clang-analyzer - check-clang-analyzer-z3 which solve those problems. Differential Revision: https://reviews.llvm.org/D50594 llvm-svn: 339629
2018-08-14 07:12:43 +08:00
USE_Z3_SOLVER=0
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
)
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
[clang] Add test dependency on llvm-as r335618 added tests that invoke llvm-as, so we should also ensure that running clang tests rebuilds llvm-as. llvm-svn: 335686
2018-06-27 07:18:59 +08:00
llvm-as
[CMake] Reformat CLANG_TEST_DEPS. llvm-svn: 250503
2015-10-16 17:38:42 +08:00
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
[clang/test] Add missing dependency on llvm-cxxfilt. This tool is needed by clang/test/CodeGen/Output/ppc-mmintrin.c. llvm-svn: 360939
2019-05-17 05:13:59 +08:00
llvm-cxxfilt
Add llvm-dis dependency to check-clang. llvm-svn: 292450
2017-01-19 08:04:44 +08:00
llvm-dis
[cmake] Add llvm-dwarfdump to clang test dependencies Commit r363496 ("[Clang] Harmonize Split DWARF options with llc", 2019-06-15) introduced the use of llvm-dwarfdump in the clang tests, so ensure the clang tests are dependent on llvm-dwarfdump. llvm-svn: 364021
2019-06-21 18:26:20 +08:00
llvm-dwarfdump
[clang] Add llvm-ifs in test deps llvm-svn: 374110
2019-10-09 04:23:24 +08:00
llvm-ifs
[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
[Clang][Bundler] Use llvm-objcopy for creating fat object files clang-offload-bundler currently uses partial linking for creating fat object files, but such technique cannot be used on Windows due to the absence of partial linking support in the linker. This patch changes implementation to use llvm-objcopy for merging device and host objects instead of doing partial linking. This is one step forward towards enabling OpenMP offload on Windows. Differential Revision: https://reviews.llvm.org/D66485 llvm-svn: 369955
2019-08-27 03:48:43 +08:00
llvm-objcopy
[CMake] Reformat CLANG_TEST_DEPS. llvm-svn: 250503
2015-10-16 17:38:42 +08:00
llvm-objdump
llvm-profdata
Fix breakage introduced by D60974 D60974 added tests which incorrectly assume that llvm-readelf is available. This is a bad assumption, it should instead declare the dependency explicitly in the tests. llvm-svn: 364855
2019-07-02 05:57:31 +08:00
llvm-readelf
[CMake] Reformat CLANG_TEST_DEPS. llvm-svn: 250503
2015-10-16 17:38:42 +08:00
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
[analyzer] [NFC] Introduce separate targets for testing the analyzer: check-clang-analyzer and check-clang-analyzer-z3 Current testing setup for analyzer tests with Z3 is rather inconvenient: There's no way to run the analyzer tests separately (I use LIT_FILTER=Analysis ninja check-clang, but a direct target is nicer). When Clang is built with Z3 support, there's no way to *not* run tests with Z3 solver, and this is often desired, as tests with Z3 solver take a very long time. This patch introduces two extra targets: - check-clang-analyzer - check-clang-analyzer-z3 which solve those problems. Differential Revision: https://reviews.llvm.org/D50594 llvm-svn: 339629
2018-08-14 07:12:43 +08:00
if (CLANG_ENABLE_STATIC_ANALYZER)
[test] Fix plugin tests Recommit of r361790 that was temporarily reverted in r361793 due to bot breakage. Summary: The following changes were required to fix these tests: 1) Change LLVM_ENABLE_PLUGINS to an option and move it to llvm/CMakeLists.txt with an appropriate default -- which matches the original default behavior. 2) Move the plugins directory from clang/test/Analysis clang/lib/Analysis. It's not enough to add an exclude to the lit.local.cfg file because add_lit_testsuites recurses the tree and automatically adds the appropriate `check-` targets, which don't make sense for the plugins because they aren't tests and don't have `RUN` statements. Here's a list of the `clang-check-anlysis*` targets with this change: ``` $ ninja -t targets all| sed -n "s/.*\/\(check[^:]*\):.*/\1/p" | sort -u | grep clang-analysis check-clang-analysis check-clang-analysis-checkers check-clang-analysis-copypaste check-clang-analysis-diagnostics check-clang-analysis-engine check-clang-analysis-exploration_order check-clang-analysis-html_diagnostics check-clang-analysis-html_diagnostics-relevant_lines check-clang-analysis-inlining check-clang-analysis-objc check-clang-analysis-unified-sources check-clang-analysis-z3 ``` 3) Simplify the logic and only include the subdirectories under clang/lib/Analysis/plugins if LLVM_ENABLE_PLUGINS is set. Reviewed By: NoQ Tags: #clang, #llvm Differential Revision: https://reviews.llvm.org/D62445 llvm-svn: 362328
2019-06-02 23:53:43 +08:00
if (LLVM_ENABLE_PLUGINS)
Fix bug in r362328 -- append to dependency list instead of overwrite it. llvm-svn: 362334
2019-06-03 01:56:26 +08:00
list(APPEND CLANG_TEST_DEPS
[test] Fix plugin tests Recommit of r361790 that was temporarily reverted in r361793 due to bot breakage. Summary: The following changes were required to fix these tests: 1) Change LLVM_ENABLE_PLUGINS to an option and move it to llvm/CMakeLists.txt with an appropriate default -- which matches the original default behavior. 2) Move the plugins directory from clang/test/Analysis clang/lib/Analysis. It's not enough to add an exclude to the lit.local.cfg file because add_lit_testsuites recurses the tree and automatically adds the appropriate `check-` targets, which don't make sense for the plugins because they aren't tests and don't have `RUN` statements. Here's a list of the `clang-check-anlysis*` targets with this change: ``` $ ninja -t targets all| sed -n "s/.*\/\(check[^:]*\):.*/\1/p" | sort -u | grep clang-analysis check-clang-analysis check-clang-analysis-checkers check-clang-analysis-copypaste check-clang-analysis-diagnostics check-clang-analysis-engine check-clang-analysis-exploration_order check-clang-analysis-html_diagnostics check-clang-analysis-html_diagnostics-relevant_lines check-clang-analysis-inlining check-clang-analysis-objc check-clang-analysis-unified-sources check-clang-analysis-z3 ``` 3) Simplify the logic and only include the subdirectories under clang/lib/Analysis/plugins if LLVM_ENABLE_PLUGINS is set. Reviewed By: NoQ Tags: #clang, #llvm Differential Revision: https://reviews.llvm.org/D62445 llvm-svn: 362328
2019-06-02 23:53:43 +08:00
SampleAnalyzerPlugin
CheckerDependencyHandlingAnalyzerPlugin
CheckerOptionHandlingAnalyzerPlugin
)
[analyzer] [NFC] Introduce separate targets for testing the analyzer: check-clang-analyzer and check-clang-analyzer-z3 Current testing setup for analyzer tests with Z3 is rather inconvenient: There's no way to run the analyzer tests separately (I use LIT_FILTER=Analysis ninja check-clang, but a direct target is nicer). When Clang is built with Z3 support, there's no way to *not* run tests with Z3 solver, and this is often desired, as tests with Z3 solver take a very long time. This patch introduces two extra targets: - check-clang-analyzer - check-clang-analyzer-z3 which solve those problems. Differential Revision: https://reviews.llvm.org/D50594 llvm-svn: 339629
2018-08-14 07:12:43 +08:00
endif()
endif()
[gen_ast_dump_json_test.py] Copy to binary directory to omit --clang argument The script will now check if a clang binary exists in the same directory and default to that instead of requiring a --clang argument. The script is copied to the clang build directory using CMake configure_file() with COPYONLY. This ensures that the version in the build directory is updated any time the source version changes. See https://reviews.llvm.org/D70119
2019-11-12 19:47:54 +08:00
# Copy gen_ast_dump_json_test.py to the clang build dir. This allows invoking
# it without having to pass the --clang= argument
[clang] [cmake] Fix gen_ast_dump_json_test.py binary dir Use correct directory to put gen_ast_dump_json_test.py instead of LLVM_BINARY_DIR. This fixes attempting to write to /usr when building clang standalone. Differential Revision: https://reviews.llvm.org/D71615
2019-12-18 01:09:18 +08:00
configure_file(AST/gen_ast_dump_json_test.py
${CLANG_BINARY_DIR}/bin/gen_ast_dump_json_test.py COPYONLY)
[gen_ast_dump_json_test.py] Copy to binary directory to omit --clang argument The script will now check if a clang binary exists in the same directory and default to that instead of requiring a --clang argument. The script is copied to the clang build directory using CMake configure_file() with COPYONLY. This ensures that the version in the build directory is updated any time the source version changes. See https://reviews.llvm.org/D70119
2019-11-12 19:47:54 +08:00
Reland "[analyzer] Add an example plugin for checker dependency handling" Buildbots complained that they couldn't find the newly added plugins. The solution was to move the check-clang cmake target closer to the bottom of the file, after the new dependencies are added. Differential Revision: https://reviews.llvm.org/D59464 llvm-svn: 360891
2019-05-16 21:22:04 +08:00
add_custom_target(clang-test-depends DEPENDS ${CLANG_TEST_DEPS})
set_target_properties(clang-test-depends PROPERTIES FOLDER "Clang tests")
add_lit_testsuite(check-clang "Running the Clang regression tests"
${CMAKE_CURRENT_BINARY_DIR}
#LIT ${LLVM_LIT}
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()