Skip to content
Snippets Groups Projects
  1. Sep 13, 2016
    • Adam Nemet's avatar
      Reapply r281276 with passing -emit-llvm in one of the tests · 8a7af2f3
      Adam Nemet authored
      Original commit message:
      
      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
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@281293 91177308-0d34-0410-b5e6-96231b3b80d8
      8a7af2f3
    • Adam Nemet's avatar
      Revert "Add -fdiagnostics-show-hotness" · 8503d694
      Adam Nemet authored
      This reverts commit r281276.
      
      Many bots are failing.
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@281279 91177308-0d34-0410-b5e6-96231b3b80d8
      8503d694
    • Adam Nemet's avatar
      Add -fdiagnostics-show-hotness · fd2a481c
      Adam Nemet authored
      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
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@281276 91177308-0d34-0410-b5e6-96231b3b80d8
      fd2a481c
  2. Sep 12, 2016
  3. Sep 04, 2016
  4. Aug 30, 2016
  5. Aug 28, 2016
  6. Aug 19, 2016
  7. Aug 18, 2016
  8. Aug 17, 2016
  9. Aug 15, 2016
  10. Aug 09, 2016
  11. Aug 06, 2016
  12. Aug 04, 2016
  13. Aug 02, 2016
  14. Jul 29, 2016
  15. Jul 28, 2016
  16. Jul 27, 2016
  17. Jul 23, 2016
  18. Jul 21, 2016
  19. Jul 18, 2016
  20. Jul 16, 2016
  21. Jul 15, 2016
  22. Jul 14, 2016
Loading