llvm-project/clang-tools-extra
Artem Dergachev f0bb45fac3 [analyzer] NFC: Move PathDiagnostic classes to libAnalysis.
At this point the PathDiagnostic, PathDiagnosticLocation, PathDiagnosticPiece
structures no longer rely on anything specific to Static Analyzer, so we can
move them out of it for everybody to use.

PathDiagnosticConsumers are still to be handed off.

Differential Revision: https://reviews.llvm.org/D67419

llvm-svn: 371661
2019-09-11 20:54:27 +00:00
..
clang-apply-replacements
clang-change-namespace
clang-doc [clang-doc] sys::fs::F_None -> OF_None. NFC 2019-09-09 12:42:10 +00:00
clang-include-fixer
clang-move
clang-query
clang-reorder-fields
clang-tidy [analyzer] NFC: Move PathDiagnostic classes to libAnalysis. 2019-09-11 20:54:27 +00:00
clangd [clangd] Collect location of macro definition in the ParsedAST 2019-09-10 10:10:36 +00:00
docs
modularize
pp-trace
test [clang-tidy] Fix bug in bugprone-use-after-move check 2019-09-09 12:59:14 +00:00
tool-template
unittests
.arcconfig
.gitignore
CMakeLists.txt
CODE_OWNERS.TXT
LICENSE.TXT
README.txt

README.txt

//===----------------------------------------------------------------------===//
// Clang Tools repository
//===----------------------------------------------------------------------===//

Welcome to the repository of extra Clang Tools.  This repository holds tools
that are developed as part of the LLVM compiler infrastructure project and the
Clang frontend.  These tools are kept in a separate "extra" repository to
allow lighter weight checkouts of the core Clang codebase.

This repository is only intended to be checked out inside of a full LLVM+Clang
tree, and in the 'tools/extra' subdirectory of the Clang checkout.

All discussion regarding Clang, Clang-based tools, and code in this repository
should be held using the standard Clang mailing lists:
  http://lists.llvm.org/mailman/listinfo/cfe-dev

Code review for this tree should take place on the standard Clang patch and
commit lists:
  http://lists.llvm.org/mailman/listinfo/cfe-commits

If you find a bug in these tools, please file it in the LLVM bug tracker:
  http://llvm.org/bugs/