aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/lldbgdbproxy.py
diff options
context:
space:
mode:
authorCarlos Galvez <carlosgalvezp@gmail.com>2025-08-23 21:41:05 +0200
committerGitHub <noreply@github.com>2025-08-23 21:41:05 +0200
commitd7390be0646821d58d104f164c693ce7f1f970cb (patch)
treeec525d3c337bcdf445759b4eb877366e70ab352b /lldb/packages/Python/lldbsuite/test/lldbgdbproxy.py
parent3ca1ca4301703ceadd0ab9c0b156bd6c0a3af7ec (diff)
downloadllvm-d7390be0646821d58d104f164c693ce7f1f970cb.zip
llvm-d7390be0646821d58d104f164c693ce7f1f970cb.tar.gz
llvm-d7390be0646821d58d104f164c693ce7f1f970cb.tar.bz2
[clang-tidy] Skip system macros in readability-identifier-naming check (#132016)
Currently, the check is processing system macros. Most importantly, it tries to find .clang-tidy files associated with those files, if the option GetConfigPerFile (on by default) is active. This is problematic for a number of reasons: - System macros cannot be acted upon (renamed), so it's wasted work. - When the main .cpp file includes a system header, clang-tidy tries to find the .clang-tidy file for that system header. When that system header is a 3rd-party repository, they may have their own .clang-tidy file, which may not be compatible with the current version of clang-tidy. So, clang-tidy may fail to analyze our main.cpp file, only because it includes a 3rd-party system header whose .clang-tidy file is incompatible with our clang-tidy binary. Therefore, skip system macros in this check. This reduces the amount of unwanted warnings as follows: On trunk: Suppressed 11448 warnings (11448 in non-user code). With this patch: Suppressed 4824 warnings (4824 in non-user code). The runtime is pretty much unchanged. Co-authored-by: Carlos Gálvez <carlos.galvez@zenseact.com>
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lldbgdbproxy.py')
0 files changed, 0 insertions, 0 deletions