lebedev.ri added a comment. In https://reviews.llvm.org/D46187#1088722, @NoQ wrote:
> It seems that you're using debug checkers of the analyzer to gain some free > tools for exploring the source code (such as displaying a call graph) for > free, right? Yes. I was interested to dump the callgraph of `DAGCombiner.cpp`, and try to analyze if there is any sane way to split it up. I think it would require a bit of changes to that callgraph dumper (writing LOC count for the functions that actually exist-as-written (or something) in the source code, grouping the functions in the main TU into a one group), but i did not get to that. > I believe we could also benefit from a method of extracting the analyzer's > `clang -cc1` run-line from clang-tidy. This would allow arbitrary debugging > over a single analyzer invocation. I'm not really following, sorry. Repository: rC Clang https://reviews.llvm.org/D46187 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
