[PATCH] D19397: Initial patch for inlining report

[Robert Cox via llvm-commits]

rcox2 added a comment.

Having a high level Report class would be useful.  I talked to a few people at the Bay Area LLVM Social and they supported the idea of Report class into which all optimizaitons could report information.

The key difference between that and the remark mechanism is that the remark mechanism provides a way to give a "blow by blow" description of what optimizations have or haven't happened in time sequence.  An optimization report (of which the inline report would be a first part) organizes the information in a more useful hierarchical and analyzable form.

Most applications that I look at have on the order of 10s of thousands of inlining decisions.  Simply having them printed out in sequence, as is done with the optimization remarks, does not yield the info in a form that guides the user to act on it.

.


http://reviews.llvm.org/D19397