aboutsummaryrefslogtreecommitdiff
path: root/llvm/unittests/Support/FileCheckTest.cpp
diff options
context:
space:
mode:
authorNikolai Kosjar <nikolai.kosjar@qt.io>2019-06-06 13:13:27 +0000
committerNikolai Kosjar <nikolai.kosjar@qt.io>2019-06-06 13:13:27 +0000
commit60e1296a9a36186656989d8223b60b6d4cb67b34 (patch)
treed789fa62cfa96907c7b4d1f195cac9f0849e094c /llvm/unittests/Support/FileCheckTest.cpp
parentdf95e6109e1cac8716bfc62ecf4500ed7420ecda (diff)
downloadllvm-60e1296a9a36186656989d8223b60b6d4cb67b34.zip
llvm-60e1296a9a36186656989d8223b60b6d4cb67b34.tar.gz
llvm-60e1296a9a36186656989d8223b60b6d4cb67b34.tar.bz2
[clang-tidy] Make the plugin honor NOLINT
Instantiate a ClangTidyDiagnosticConsumer also for the plugin case and let it forward the diagnostics to the external diagnostic engine that is already in place. One minor difference to the clang-tidy executable case is that the compiler checks/diagnostics are referred to with their original name. For example, for -Wunused-variable the plugin will refer to the check as "-Wunused-variable" while the clang-tidy executable will refer to that as "clang-diagnostic- unused-variable". This is because the compiler diagnostics never reach ClangTidyDiagnosticConsumer. Differential Revision: https://reviews.llvm.org/D61487 llvm-svn: 362702
Diffstat (limited to 'llvm/unittests/Support/FileCheckTest.cpp')
0 files changed, 0 insertions, 0 deletions