llvm-project/clang
Keno Fischer 6f48c07620 [analyzer] Add werror flag for analyzer warnings
Summary:
We're using the clang static analyzer together with a number of
custom analyses in our CI system to ensure that certain invariants
are statiesfied for by the code every commit. Unfortunately, there
currently doesn't seem to be a good way to determine whether any
analyzer warnings were emitted, other than parsing clang's output
(or using scan-build, which then in turn parses clang's output).
As a simpler mechanism, simply add a `-analyzer-werror` flag to CC1
that causes the analyzer to emit its warnings as errors instead.
I briefly tried to have this be `Werror=analyzer` and make it go
through that machinery instead, but that seemed more trouble than
it was worth in terms of conflicting with options to the actual build
and special cases that would be required to circumvent the analyzers
usual attempts to quiet non-analyzer warnings. This is simple and it
works well.

Reviewed-By: NoQ, Szelethusw
Differential Revision: https://reviews.llvm.org/D62885

llvm-svn: 362855
2019-06-07 23:34:00 +00:00
..
INPUTS
bindings [CodeComplete] Update python tests after r360042 2019-05-06 14:56:24 +00:00
cmake Use LTO capable linker 2019-06-05 17:35:38 +00:00
docs AST Matchers tutorial requests to enable clang-tools-extra. NFC 2019-06-07 16:31:06 +00:00
examples [PragmaHandler] Expose `#pragma` location 2019-05-21 23:51:38 +00:00
include [analyzer] Add werror flag for analyzer warnings 2019-06-07 23:34:00 +00:00
lib [analyzer] Add werror flag for analyzer warnings 2019-06-07 23:34:00 +00:00
runtime [GWP-ASan] Mutex implementation [2]. 2019-05-30 19:45:32 +00:00
test [analyzer] Add werror flag for analyzer warnings 2019-06-07 23:34:00 +00:00
tools Revert "[Support][Test] Time profiler: add regression test" 2019-06-07 18:35:58 +00:00
unittests clang-format: better handle namespace macros 2019-06-06 20:06:23 +00:00
utils [analyzer] exploded-graph-rewriter: Add the missing license header! 2019-06-05 02:09:49 +00:00
www [Analyzer] Checker for non-determinism caused by iteration of unordered container of pointers 2019-05-24 19:24:08 +00:00
.arcconfig
.clang-format
.clang-tidy Disable tidy checks with too many hits 2019-02-01 11:20:13 +00:00
.gitignore Adjust documentation for git migration. 2019-01-29 16:37:27 +00:00
CMakeLists.txt Moved everything SMT-related to LLVM and updated the cmake scripts. 2019-03-25 17:47:45 +00:00
CODE_OWNERS.TXT Add myself as code owner for OpenBSD driver 2018-11-30 21:42:34 +00:00
INSTALL.txt
LICENSE.TXT Fix typos throughout the license files that somehow I and my reviewers 2019-01-21 09:52:34 +00:00
ModuleInfo.txt
NOTES.txt PTH-- Remove feature entirely- 2018-12-04 14:34:09 +00:00
README.txt

README.txt

//===----------------------------------------------------------------------===//
// C Language Family Front-end
//===----------------------------------------------------------------------===//

Welcome to Clang.  This is a compiler front-end for the C family of languages
(C, C++, Objective-C, and Objective-C++) which is built as part of the LLVM
compiler infrastructure project.

Unlike many other compiler frontends, Clang is useful for a number of things
beyond just compiling code: we intend for Clang to be host to a number of
different source-level tools.  One example of this is the Clang Static Analyzer.

If you're interested in more (including how to build Clang) it is best to read
the relevant web sites.  Here are some pointers:

Information on Clang:             http://clang.llvm.org/
Building and using Clang:         http://clang.llvm.org/get_started.html
Clang Static Analyzer:            http://clang-analyzer.llvm.org/
Information on the LLVM project:  http://llvm.org/

If you have questions or comments about Clang, a great place to discuss them is
on the Clang development mailing list:
  http://lists.llvm.org/mailman/listinfo/cfe-dev

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