llvm-project

Go to file

Alexander Kornienko 4aca9b1cd8 Expose the name of the checker producing each diagnostic message.

Summary:
In clang-tidy we'd like to know the name of the checker producing each
diagnostic message. PathDiagnostic has BugType and Category fields, which are
both arbitrary human-readable strings, but we need to know the exact name of the
checker in the form that can be used in the CheckersControlList option to
enable/disable the specific checker.

This patch adds the CheckName field to the CheckerBase class, and sets it in
the CheckerManager::registerChecker() method, which gets them from the
CheckerRegistry.

Checkers that implement multiple checks have to store the names of each check
in the respective registerXXXChecker method.

Reviewers: jordan_rose, krememek

Reviewed By: jordan_rose

CC: cfe-commits

Differential Revision: http://llvm-reviews.chandlerc.com/D2557

llvm-svn: 201186

2014-02-11 21:49:21 +00:00

clang

Expose the name of the checker producing each diagnostic message.

2014-02-11 21:49:21 +00:00

clang-tools-extra

The diagnostic printer expects the LangOptions to still be alive. Give it one that lives at least as long as all the uses of it. This is still wrong though, we should be passing in the correct LangOpts for a given source file.

2014-02-06 22:57:16 +00:00

compiler-rt

Require CMake 2.8.12.1 or later on Windows

2014-02-11 21:46:19 +00:00

debuginfo-tests

don't use CHECK-NEXT because it may be on the same line.