]> granicus.if.org Git - clang/commit
[analyzer] [NFC] Introduce separate targets for testing the analyzer: check-clang...
authorGeorge Karpenkov <ekarpenkov@apple.com>
Mon, 13 Aug 2018 23:12:43 +0000 (23:12 +0000)
committerGeorge Karpenkov <ekarpenkov@apple.com>
Mon, 13 Aug 2018 23:12:43 +0000 (23:12 +0000)
commit4fb8974a97cc95e76b5f1c5ac04dc97abc621366
treeecb960ba6fb5b65a59538a34d6093d5e22010b42
parent09d5c6b600bdab633bffe2b2df25a7fbb8cad784
[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

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@339629 91177308-0d34-0410-b5e6-96231b3b80d8
test/Analysis/analyzer_test.py
test/Analysis/lit.local.cfg
test/CMakeLists.txt
test/lit.site.cfg.py.in