<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 8/14/19 9:20 AM, Reid Kleckner wrote:<br>
<blockquote type="cite"
cite="mid:CACs=ty+TmFJ6i1=1BiNeQo7aSgYpTnpk8MEcnn0Gc-Lb2aUbWQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Wed, Aug 14, 2019 at 12:24 AM Dmitri Gribenko
via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org"
moz-do-not-send="true">cfe-dev@lists.llvm.org</a>> wrote:</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
I would like to suggest something different: move Clang
Static<br>
Analyzer to clang-tools-extra. Build it either as a separate
binary or<br>
compile it into the clang-tidy binary. Then let `clang
-analyze`<br>
delegate to that binary for backwards compatibility.<br>
</blockquote>
<div><br>
</div>
<div>Speaking as an outsider in the peanut gallery who does
very little static analysis, this is very appealing to me.
It would save binary size in clang and make building and
testing clang faster, if the developer isn't working in the
static analyzer space.</div>
</div>
</div>
</blockquote>
<br>
Generally we already have a cmake flag for this,
-DCLANG_ENABLE_STATIC_ANALYZER=OFF (defaults to ON). This flag is
definitely a must-have for people who try to make their clang binary
as tiny as possible. But i understand that this flag is not
exceptionally discoverable and a lot of people probably suffer
unnecessarily long compile times simply because they didn't discover
it.<br>
<br>
That said, i suspect that unless you work exclusively on CodeGen,
you probably do not want to turn off the Static Analyzer, because
the Static Analyzer has some interesting tests that you can
accidentally break when you work on anything else (Preprocessor,
Lexer, AST, Sema...). In particular, Richard Smith regularly touches
our code :)<br>
</body>
</html>