<div dir="ltr">Another possible (not mutually exclusive) extension point to add static analysis into would be through the Tooling interface and compilation databases - this would allow just the analysis to be run, without making it part of a build (no one would make static analysis part of an interactive build, it's too slow, right? the only reason it was integrated into the build with scan-build was because it was the best way to discover the build commands - but the Tooling/Compilation Database system allows us to separate build discovery from tool execution)</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 2, 2016 at 6:19 AM, Craig, Ben via cfe-dev <span dir="ltr"><<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
I'm all for this idea. There is precedent for this in other tools
(Visual Studio's /analyze). I think it also greatly reduces the
need for build interposition via scan-build.<br>
<br>
I would ask that you think carefully about the output format of the
detailed analysis for -enable-analyze-pass. If people are using
-enable-analyze-pass on most of their builds, then plist and html
reports are likely to go unread for the most part. Consider making
"no detailed analysis" an option for -enable-analyze-pass to help
with these use cases.<div><div class="h5"><br>
<br>
<div>On 1/29/2016 9:04 PM, <Alexander G.
Riccio> via cfe-dev wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">
<div>As mentioned by myself, Aaron Ballman, and Philip Reames,
in a reply to "Proposal: Integrate static analysis test
suites", the fact that static analysis generates a totally
different set of warnings than compilation (not a superset),
is surprising to some.</div>
<div><br>
</div>
<div>One possibility, in order to preserve the current behavior
for any tools that rely on this, is to add an option to clang,
something like "-enable-analyze-pass" that the user can
specify to run analysis AND compilation.</div>
<div><br>
</div>
<div>Thoughts?</div>
<br clear="all">
<div>
<div>
<div dir="ltr">
<div>
<div dir="ltr"><span style="font-size:12.8px">Sincerely,</span><br style="font-size:12.8px">
<span style="font-size:12.8px">Alexander Riccio</span><br style="font-size:12.8px">
<span style="font-size:12.8px">--</span><br style="font-size:12.8px">
<span style="font-size:12.8px">"Change the world or go
home."</span>
<div style="font-size:12.8px"><a href="http://about.me/ariccio" target="_blank">about.me/ariccio</a></div>
<div style="font-size:12.8px"><a href="http://about.me/ariccio" target="_blank"><br>
</a></div>
<div style="font-size:12.8px">If left to my own
devices, I will build more.</div>
<div style="font-size:12.8px">⁂</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
cfe-dev mailing list
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><span class="HOEnZb"><font color="#888888">
</font></span></pre><span class="HOEnZb"><font color="#888888">
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
<pre cols="72">--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
</pre>
</font></span></div>
<br>_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
<br></blockquote></div><br></div>