Add -fdiagnostics-show-hotness
authorAdam Nemet <anemet@apple.com>
Mon, 12 Sep 2016 23:48:16 +0000 (23:48 +0000)
committerAdam Nemet <anemet@apple.com>
Mon, 12 Sep 2016 23:48:16 +0000 (23:48 +0000)
commita340eff335cfa88403afc2ee81babceaba101965
tree19404cbdd04bb9a21b2f3b17c24003346680e316
parentd2a4da09ad3f4a632cd4de61406c57ca66ccde50
Add -fdiagnostics-show-hotness

Summary:
I've recently added the ability for optimization remarks to include the
hotness of the corresponding code region.  This uses PGO and allows
filtering of the optimization remarks by relevance.  The idea was first
discussed here:
http://thread.gmane.org/gmane.comp.compilers.llvm.devel/98334

The general goal is to produce a YAML file with the remarks.  Then, an
external tool could dynamically filter these by hotness and perhaps by
other things.

That said it makes sense to also expose this at the more basic level
where we just include the hotness info with each optimization remark.
For example, in D22694, the clang flag was pretty useful to measure the
overhead of the additional analyses required to include hotness.
(Without the flag we don't even run the analyses.)

For the record, Hal has already expressed support for the idea of this
patch on IRC.

Differential Revision: https://reviews.llvm.org/D23284

llvm-svn: 281276
clang/docs/UsersManual.rst
clang/include/clang/Basic/DiagnosticDriverKinds.td
clang/include/clang/Driver/Options.td
clang/include/clang/Frontend/CodeGenOptions.def
clang/lib/CodeGen/CodeGenAction.cpp
clang/lib/Driver/Tools.cpp
clang/lib/Frontend/CompilerInvocation.cpp
clang/test/Frontend/Inputs/optimization-remark-with-hotness.proftext [new file with mode: 0644]
clang/test/Frontend/optimization-remark-with-hotness.c [new file with mode: 0644]