<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 14, 2009, at 6:53 PM, Zhongxing Xu wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">On Wed, Jul 15, 2009 at 8:33 AM, Ted Kremenek<<a href="mailto:kremenek@apple.com">kremenek@apple.com</a>> wrote:<br><blockquote type="cite">On Jul 13, 2009, at 6:31 AM, Zhongxing Xu wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">This is an initial implementation of call graph building based on pch<br></blockquote><blockquote type="cite">reader and the new Program/Entity facility. It is very primitive but<br></blockquote><blockquote type="cite">functional.<br></blockquote><blockquote type="cite">Put the files under clang/tools/wpa (meaning 'whole program<br></blockquote><blockquote type="cite">analysis'). After 'make', a new command 'clang-analyze' will be<br></blockquote><blockquote type="cite">generated. It takes a list of .ast files and build call graph over<br></blockquote><blockquote type="cite">them.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Hi Zhongxing,<br></blockquote><blockquote type="cite">I would call the program 'clang-callgraph' so that people don't confuse it<br></blockquote><blockquote type="cite">with the "static analyzer". Comments inline.<br></blockquote><br>Hi Ted & Daniel,<br><br>My original intention is not to make this a standalone callgraph tool.<br>I intend it to gradually become the whole program analysis driver. And<br>the first step usually is to build the call graph. Thus I call it<br>'clang-analyzer'.<br></span></blockquote><div><br></div><div>clang-wpa? clang-analyzer will really confuse casual users.</div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><br>When CallGraph.h CallGraph.cpp becomes mature enough, I would like it<br>to be moved into libAnalysis or elsewhere suitable.</span></blockquote></div><br><div>I don't see much of a reason to not include CallGraph.[h,cpp] in libAnalysis from the onset and then have the driver use it. Being in one library or another doesn't officially "bless" it as being mature. For example, C++ support in Clang isn't fully "mature", but it is spread across the various libraries. Including CallGraph.[h,cpp] in libAnalysis (if that is the eventual home) forces you to maintain a library-based design for that class.</div></body></html>