<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 30, 2013, at 7:28 , David Blaikie <<a href="mailto:dblaikie@gmail.com">dblaikie@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p dir="ltr"><br>
On May 30, 2013 5:55 AM, "Robert Henry" <<a href="mailto:rrh@newrelic.com">rrh@newrelic.com</a>> wrote:<br>
><br>
> I have two source files each of which is analyzed independently<br>
> without error by scan-build. However, the combination of the 2 files<br>
> should trigger a complaint from scan-build, assuming scan-build has<br>
> inter-procedural analysis spanning the two compilation units.</p><p dir="ltr">That assumption would be incorrect. The Clang Static Analyzer has no cross-TU power at the moment.</p></blockquote>Right. scan-build's job is simply to find out which files you want to compile (more useful when you have a build system rather than a single explicit build command). Analysis is still done on each TU separately.</div><div><br></div><div>Sorry!</div><div>Jordan</div><br></body></html>