rjmccall added a comment. This discussion of the command line interface makes me think that we should be taking Richard's suggestion one step further. Why is Clang's involvement here more than just handing down specific requests for optimization data to LLVM and packaging that information back into some reasonable format? The actual presentation of that data seems like it belongs in a separate library / tool, which can have a rich set of visualization options. This is also a more rigorously testable design, since the tool has a well-defined input format that's not just an incidental by-product of the compiler.
If we did that, then Clang just needs (1) an output filename, (2) an optional list of passes to collect data from, and (3) maybe some stringly-typed configuration data for each. http://reviews.llvm.org/D19678 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
