4 Commits

Author	SHA1	Message	Date
Brian Gesiak	4ef3daafef	[ORE] Add diagnostics hotness threshold ... Summary: Add an option to prevent diagnostics that do not meet a minimum hotness threshold from being output. When generating optimization remarks for large codebases with a ton of cold code paths, this option can be used to limit the optimization remark output at a reasonable size. Discussion of this change can be read here: http://lists.llvm.org/pipermail/llvm-dev/2017-June/114377.html Reviewers: anemet, davidxl, hfinkel Reviewed By: anemet Subscribers: qcolombet, javed.absar, fhahn, eraman, llvm-commits Differential Revision: https://reviews.llvm.org/D34867 llvm-svn: 306912	2017-06-30 23:14:53 +00:00
Adam Nemet	916923e689	[llc] Add -pass-remarks-output ... This is the opt/llc counterpart of -fsave-optimization-record to output optimization remarks in a YAML file. llvm-svn: 293121	2017-01-26 00:39:51 +00:00
Adam Nemet	2ada300821	[llc] Add -pass-remarks-with-hotness ... Analogous to the code in opt, this enables hotness in opt-remarks. llvm-svn: 293113	2017-01-25 23:55:59 +00:00
Adam Nemet	a964066705	New OptimizationRemarkEmitter pass for MIR ... This allows MIR passes to emit optimization remarks with the same level of functionality that is available to IR passes. It also hooks up the greedy register allocator to report spills. This allows for interesting use cases like increasing interleaving on a loop until spilling of registers is observed. I still need to experiment whether reporting every spill scales but this demonstrates for now that the functionality works from llc using -pass-remarks*=<pass>. Differential Revision: https://reviews.llvm.org/D29004 llvm-svn: 293110	2017-01-25 23:20:33 +00:00