llvm-project/clang/test/Analysis/ctu-lookup-name-with-space.cpp
Donát Nagy c3f8dd1228
[NFC][analyzer] Use %clang_analyze_cc1 consistently (#145895)
A large majority of the LIT tests of the clang static analyzer use RUN
lines with the placeholder `%clang_analyze_cc1` which expands to
`%clang_cc1 -analyze -setup-static-analyzer` where the only effect of
`-setup-static-analyzer` is that it ensures that the macro
`__clang_analyzer__` is defined. However, there were some tests that
used `%clang_cc1 -analyze` directly; this commit changes those to using
`%clang_analyze_cc1` for the sake of consistency.

Previously `%clang_analyze_cc1` did not work within the directory
`exploded-graph-rewriter` (because that directory has its own custom
`lit.local.cfg`) but this problem was eliminated by the recent commit
40cc4379cda6e0d6efe72c55d1968f9cf427a16a, so it was possible to resolve
and delete the FIXME comments asking for this change.

There are a few tests that use `%clang --analyze` or other command-line
flags (e.g. help flags), those are not affected by this change.

This cleanup was discussed in the discourse thread
https://discourse.llvm.org/t/taking-ownership-of-clang-test-analysis/84689/11
2025-06-30 12:59:51 +02:00

42 lines
1.7 KiB
C++

// RUN: rm -rf %t
// RUN: mkdir %t
// RUN: echo '41:c:@S@G@F@G#@Sa@F@operator void (*)(int)#1 %/t/importee.ast' >> %t/externalDefMap.txt
// RUN: echo '38:c:@S@G@F@G#@Sa@F@operator void (*)()#1 %/t/importee.ast' >> %t/externalDefMap.txt
// RUN: echo '14:c:@F@importee# %/t/importee.ast' >> %t/externalDefMap.txt
// RUN: %clang_cc1 -emit-pch %/S/Inputs/ctu-lookup-name-with-space.cpp -o %t/importee.ast
// RUN: cd %t
// RUN: %clang_analyze_cc1 \
// RUN: -analyzer-checker=core \
// RUN: -analyzer-config experimental-enable-naive-ctu-analysis=true \
// RUN: -analyzer-config ctu-dir=. \
// RUN: -analyzer-config display-ctu-progress=true \
// RUN: -verify %s 2>&1 | FileCheck %s
// CHECK: CTU loaded AST file
// FIXME: In this test case, we cannot use the on-demand-parsing approach to
// load the external TU.
//
// In the Darwin system, the target triple is determined by the driver,
// rather than using the default one like other systems. However, when
// using bare `clang -cc1`, the adjustment is not done, which cannot
// match the one loaded with on-demand-parsing (adjusted triple).
// We bypass this problem by loading AST files, whose target triple is
// also unadjusted when generated via `clang -cc1 -emit-pch`.
//
// Refer to: https://discourse.llvm.org/t/60762
//
// This is also the reason why the test case of D75665 (introducing
// the on-demand-parsing feature) is enabled only on Linux.
void importee();
void trigger() {
// Call an external function to trigger the parsing process of CTU index.
// Refer to file Inputs/ctu-lookup-name-with-space.cpp for more details.
importee(); // expected-no-diagnostics
}