[cfe-dev] Getting involved with Clang refactoring

Manuel Klimek klimek at google.com
Tue May 29 11:00:19 PDT 2012

On Tue, May 29, 2012 at 7:43 PM, Joerg Sonnenberger <joerg at britannica.bec.de
> wrote:

> On Tue, May 29, 2012 at 06:50:11PM +0200, Manuel Klimek wrote:
> > Yes. But if you want to statically analyze a whole code base for global
> > information, you need to analyze every TU (as you would need to compile
> > every TU). Having a dependency graph restriction in here would lead to
> > sequential bottlenecks (which make -j shows).
> This part I don't understand. What kind of dependency graph restrictions
> are you thinking about? If you have functional dependencies of one TU on
> another TU, you can't just drop those. Consider build tools like yacc for
> an integrated OS build as example.

This is exactly what I meant when I wrote: "On the other hand, having
global analysis of course still relies on the build, as generated sources
need to be available. But given that we often want to run multiple
iterations of static analysis at a single point of the code, this pays of
big time."

Note that this is *not* about running something when you change code
(that's what build tools are for), but to run a tool when you want to
change something, or to run multiple static analysis runs on the same code

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20120529/485ef2d2/attachment.html>

More information about the cfe-dev mailing list