[cfe-dev] Clang Static Analyzer without scan-build

[Aditya Kumar]

> -----Original Message-----
> From: cfe-dev-bounces at cs.uiuc.edu [mailto:cfe-dev-bounces at cs.uiuc.edu]
> On Behalf Of Richard
> Sent: Wednesday, July 31, 2013 4:33 PM
> To: cfe-dev at cs.uiuc.edu
> Subject: Re: [cfe-dev] Clang Static Analyzer without scan-build
> 
> 
> In article <001101ce8d6d$1019efd0$304dcf70$@codeaurora.org>,
>     "Aditya Kumar" <hiraditya at codeaurora.org> writes:
> 
> > This will have an overhead on the overall compilation time which is
> > often not the desirable thing. [...]
> >
> > I wanted some feedback if this is a good idea or not.
> 
> On a code base where I can build the entire tree with gcc 4.6 in about
> 10 minutes, running the static analyzer took multiple hours.  I didn't
time it
> exactly because I wasn't expecting THAT much of a slowdown.
That is just a one-time overhead. The next time you run the static analyzer
it should take very less time, because the static analyzer will take
advantage of the incremental build system.

> 
> So, based on that experience, anything that makes this lengthy process
take
> even longer would be a thumbs down from me.

Having compile-and-analyze flag takes 'less' time than scan-build. The
overhead I was talking about is the 'little-extra' time every time the
program is built during the development process.
It will give some useful static analysis information with every build, I
hope.

> "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-
> pipeline>
>      The Computer Graphics Museum <http://computergraphicsmuseum.org>
>          The Terminals Wiki <http://terminals.classiccmp.org>
>   Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev