summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Target/WebAssembly/WebAssemblyExplicitLocals.cpp
diff options
context:
space:
mode:
authorGeorge Karpenkov <ekarpenkov@apple.com>2018-08-13 23:12:43 +0000
committerGeorge Karpenkov <ekarpenkov@apple.com>2018-08-13 23:12:43 +0000
commit2997a3042e41dfc1d842fbe7be8a7777454ad4b5 (patch)
treec9dbda3b28f055831d4205720ac2080ab991222c /llvm/lib/Target/WebAssembly/WebAssemblyExplicitLocals.cpp
parent97ea485041c49fdfe0c3bac95d88753b4a461144 (diff)
downloadbcm5719-llvm-2997a3042e41dfc1d842fbe7be8a7777454ad4b5.tar.gz
bcm5719-llvm-2997a3042e41dfc1d842fbe7be8a7777454ad4b5.zip
[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
Diffstat (limited to 'llvm/lib/Target/WebAssembly/WebAssemblyExplicitLocals.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud