Skip to content
  1. Feb 16, 2010
  2. Feb 13, 2010
  3. Feb 05, 2010
  4. Jan 19, 2010
    • Dan Gohman's avatar
      When doing address-mode sinking, expand the base register first, rather · ca19445d
      Dan Gohman authored
      than the scaled register. This makes it more likely that subsequent
      AddrModeMatcher queries will match the new address the same way as the
      old, instead of accidentally matching what had been the base register
      as the new scaled register, and then failing to match the scaled register.
      This fixes some problems with address-mode sinking multiple muls into a
      block, which will be a lot more common with some upcoming
      LoopStrengthReduction changes.
      
      llvm-svn: 93935
      ca19445d
  5. Jan 05, 2010
  6. Dec 17, 2009
  7. Dec 08, 2009
  8. Dec 03, 2009
  9. Oct 31, 2009
  10. Oct 16, 2009
  11. Sep 16, 2009
  12. Sep 02, 2009
  13. Aug 26, 2009
  14. Aug 23, 2009
  15. Aug 13, 2009
  16. Aug 12, 2009
  17. Aug 11, 2009
  18. Jul 31, 2009
  19. Jul 25, 2009
  20. Jul 22, 2009
  21. Jul 20, 2009
  22. Jul 10, 2009
  23. Jul 03, 2009
  24. Jun 15, 2009
  25. Jun 02, 2009
  26. May 04, 2009
  27. Apr 07, 2009
  28. Mar 27, 2009
  29. Mar 26, 2009
  30. Mar 13, 2009
  31. Mar 12, 2009
    • Duncan Sands's avatar
      Revert commit 66140 since it caused several failures · 1f853d6a
      Duncan Sands authored
      in the Ada testcase.  Reverting this only covers up
      the real problem, which is a nasty conceptual difficulty
      in the phi elimination pass: when eliminating phi nodes
      in landing pads, the register copies need to come before
      the invoke, not at the end of the basic block which is
      too late...  See PR3784.
      
      llvm-svn: 66826
      1f853d6a
  32. Mar 05, 2009
  33. Feb 20, 2009
  34. Feb 13, 2009
  35. Feb 12, 2009
  36. Jan 23, 2009
    • Gabor Greif's avatar
      Simplify the logic of getting hold of a PHI predecessor block. · eb61fcf2
      Gabor Greif authored
      There is now a direct way from value-use-iterator to incoming block in PHINode's API.
      This way we avoid the iterator->index->iterator trip, and especially the costly
      getOperandNo() invocation. Additionally there is now an assertion that the iterator
      really refers to one of the PHI's Uses.
      
      llvm-svn: 62869
      eb61fcf2
  37. Jan 18, 2009
Loading