Skip to content
  1. Apr 02, 2008
  2. Apr 01, 2008
  3. Mar 24, 2008
    • Evan Cheng's avatar
      Increasing the inline limit from (overly conservative) 200 to 300. Given each... · 3471ae8c
      Evan Cheng authored
      Increasing the inline limit from (overly conservative) 200 to 300. Given each BB costs 20 and each instruction costs 5, 200 means a 4 BB function + 24 instructions (actually less because caller's size also contributes to it).
      
      Furthermore, double the limit when more than 10% of the callee instructions are vector instructions. Multimedia kernels tend to love inlining.
      
      llvm-svn: 48725
      3471ae8c
  4. Mar 23, 2008
  5. Mar 20, 2008
  6. Mar 13, 2008
  7. Mar 11, 2008
  8. Mar 10, 2008
  9. Mar 09, 2008
  10. Mar 07, 2008
  11. Mar 05, 2008
  12. Mar 04, 2008
  13. Feb 20, 2008
  14. Feb 19, 2008
  15. Feb 18, 2008
  16. Feb 14, 2008
  17. Feb 05, 2008
  18. Jan 27, 2008
  19. Jan 26, 2008
  20. Jan 25, 2008
  21. Jan 12, 2008
  22. Jan 11, 2008
  23. Jan 03, 2008
  24. Dec 29, 2007
  25. Dec 25, 2007
    • Gordon Henriksen's avatar
      GC poses hazards to the inliner. Consider: · b969c598
      Gordon Henriksen authored
          define void @f() {
                  ...
                  call i32 @g()
                  ...
          }
      
          define void @g() {
                  ...
          }
      
      The hazards are:
      
        - @f and @g have GC, but they differ GC. Inlining is invalid. This
          may never occur.
        - @f has no GC, but @g does. g's GC must be propagated to @f.
      
      The other scenarios are safe:
      
        - @f and @g have the same GC.
        - @f and @g have no GC.
        - @g has no GC.
      
      This patch adds inliner checks for the former two scenarios.
      
      llvm-svn: 45351
      b969c598
  26. Dec 22, 2007
Loading