Skip to content
Snippets Groups Projects
  1. Sep 11, 2015
  2. Sep 10, 2015
  3. Sep 02, 2015
  4. Sep 01, 2015
  5. Aug 28, 2015
  6. Aug 27, 2015
  7. Aug 24, 2015
  8. Aug 18, 2015
  9. Aug 14, 2015
  10. Aug 12, 2015
  11. Aug 11, 2015
  12. Aug 10, 2015
    • Nick Lewycky's avatar
      Fix typo. · 1525c826
      Nick Lewycky authored
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@244490 91177308-0d34-0410-b5e6-96231b3b80d8
      1525c826
    • Mark Heffernan's avatar
      Add new llvm.loop.unroll.enable metadata for use with "#pragma unroll". · 1476822d
      Mark Heffernan authored
      This change adds the new unroll metadata "llvm.loop.unroll.enable" which directs
      the optimizer to unroll a loop fully if the trip count is known at compile time, and
      unroll partially if the trip count is not known at compile time. This differs from
      "llvm.loop.unroll.full" which explicitly does not unroll a loop if the trip count is not
      known at compile time
      
      With this change "#pragma unroll" generates "llvm.loop.unroll.enable" rather than
      "llvm.loop.unroll.full" metadata. This changes the semantics of "#pragma unroll" slightly
      to mean "unroll aggressively (fully or partially)" rather than "unroll fully or not at all".
      
      The motivating example for this change was some internal code with a loop marked
      with "#pragma unroll" which only sometimes had a compile-time trip count depending
      on template magic. When the trip count was a compile-time constant, everything works
      as expected and the loop is fully unrolled. However, when the trip count was not a
      compile-time constant the "#pragma unroll" explicitly disabled unrolling of the loop(!).
      Removing "#pragma unroll" caused the loop to be unrolled partially which was desirable
      from a performance perspective.
      
      
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@244467 91177308-0d34-0410-b5e6-96231b3b80d8
      1476822d
    • Roman Kashitsyn's avatar
      Add WebKit brace style configuration option. · 8aef53c9
      Roman Kashitsyn authored
      Summary:
      Add brace style `BS_WebKit` as described on https://www.webkit.org/coding/coding-style.html:
      
      * Function definitions: place each brace on its own line.
      * Other braces: place the open brace on the line preceding the code block; place the close brace on its own line.
      
      Set brace style used in `getWebKitStyle()` to the newly added `BS_WebKit`.
      
      Reviewers: djasper, klimek
      
      Subscribers: klimek, cfe-commits
      
      Differential Revision: http://reviews.llvm.org/D11837
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@244446 91177308-0d34-0410-b5e6-96231b3b80d8
      8aef53c9
  13. Aug 05, 2015
  14. Aug 03, 2015
  15. Jul 31, 2015
  16. Jul 28, 2015
  17. Jul 24, 2015
  18. Jul 23, 2015
  19. Jul 22, 2015
  20. Jul 17, 2015
  21. Jul 15, 2015
  22. Jul 13, 2015
  23. Jul 12, 2015
  24. Jul 09, 2015
    • Diego Novillo's avatar
      Add GCC-compatible flags -fprofile-generate and -fprofile-use. · 9b5c02e4
      Diego Novillo authored
      This patch adds support for specifying where the profile is emitted in a
      way similar to GCC. These flags are used to specify directories instead
      of filenames. When -fprofile-generate=DIR is used, the compiler will
      generate code to write to <DIR>/default.profraw.
      
      The patch also adds a couple of extensions: LLVM_PROFILE_FILE can still be
      used to override the directory and file name to use and -fprofile-use
      accepts both directories and filenames.
      
      To simplify the set of flags used in the backend, all the flags get
      canonicalized to -fprofile-instr-{generate,use} when passed to the
      backend. The decision to use a default name for the profile is done
      in the driver.
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@241825 91177308-0d34-0410-b5e6-96231b3b80d8
      9b5c02e4
Loading