[cfe-dev] C++ analysis with Clang?

Anna Zaks ganna at apple.com
Mon Jun 4 16:39:16 PDT 2012

On Jun 4, 2012, at 4:20 PM, Karl Mazurak wrote:

> On 06/04/2012 02:40 PM, Manuel Klimek wrote:
>> what we do is outputting strings of (key, value) pairs from the analysis
>> and later  fold those via an outside script;
> That's roughly what we were thinking about starting off with, which sounds like it should work fine with a plugin.  (Unless I'm overlooking something?)
>> you can use python or somesuch for the post-processing
> Speaking of which, there isn't official documentation for the LibClang Python bindings yet, is there?
> On 06/04/2012 04:57 PM, Anna Zaks wrote:
>> You can use ViewCFG and DumpCFG checkers to see how C++ statements are
>> modeled (and what the deficiencies are):
>> *clang -cc1 -analyze -analyzer-checker=debug.ViewCFG test.c*
> Hmm, my copy is still a bit out of date, but I'm getting nothing for ViewCFG; DumpCFG works fine, though.
debug.ViewCFG output is based on Graphviz: http://llvm.org/docs/ProgrammersManual.html#ViewGraph
> Also, is either of these formats meant to be read back in?  In case we end up needing more detail in our whole program analyses.
No. I don't think we have any CFG serialization mechanisms.

Also, Tooling infrastructure and the static analyzer are not currently integrated. The analyzer is relying on scan-build script to interpose itself on a build. Tooling is a new infrastructure which has been used for AST analyzes based projects like refactoring.

> On 06/04/2012 06:06 PM, Jim Goodnow II wrote:
>> Actually, except for some of the new c++11 concepts like lambdas, most
>> are currently handled and the analyzer can already be very useful for
>> C++ programs.
> Ah, good to know.
> Thanks, all of you!
> -- 
> Karl

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20120604/3d3eb835/attachment.html>

More information about the cfe-dev mailing list