Skip to content
  1. Feb 20, 2007
  2. Feb 08, 2007
    • Evan Cheng's avatar
      Fixed a long standing spiller bug that's exposed by Thumb: · 6ad6fdb7
      Evan Cheng authored
      The code sequence before the spiller is something like:
                       = tMOVrr
              %reg1117 = tMOVrr
              %reg1078 = tLSLri %reg1117, 2
      
      The it starts spilling:
              %r0 = tRestore <fi#5>, 0
              %r1 = tRestore <fi#7>, 0
              %r1 = tMOVrr %r1<kill>
              tSpill %r1, <fi#5>, 0
              %reg1078 = tLSLri %reg1117, 2
      
      It restores the value while processing the first tMOVrr. At this point, the
      spiller remembers fi#5 is available in %r0. Next it processes the second move.
      It restores the source before the move and spills the result afterwards. The
      move becomes a noop and is deleted. However, a spill has been inserted and that
      should invalidate reuse of %r0 for fi#5 and add reuse of %r1 for fi#5.
      Therefore, %reg1117 (which is also assigned fi#5) should get %r1, not %r0.
      
      llvm-svn: 34039
      6ad6fdb7
  3. Jan 23, 2007
  4. Jan 19, 2007
    • Evan Cheng's avatar
      GetRegForReload() now keeps track which registers have been considered and... · fc74e2de
      Evan Cheng authored
      GetRegForReload() now keeps track which registers have been considered and rejected during its quest to find a suitable reload register. This avoids an infinite loop in case like this:
        t1 := op t2, t3
        t2 <- assigned r0 for use by the reload but ended up reuse r1
        t3 <- assigned r1 for use by the reload but ended up reuse r0
        t1 <- desires r1
              sees r1 is taken by t2, tries t2's reload register r0
              sees r0 is taken by t3, tries t3's reload register r1
              sees r1 is taken by t2, tries t2's reload register r0 ...
      
      llvm-svn: 33382
      fc74e2de
  5. Dec 19, 2006
  6. Dec 17, 2006
  7. Dec 15, 2006
  8. Dec 14, 2006
    • Evan Cheng's avatar
      Fix a long-standing spiller bug: · 4c306ae0
      Evan Cheng authored
      If a spillslot value is available in a register, and there is a noop copy that
      targets that register, the spiller correctly decide not to invalidate the
      spillslot register.
      
      However, even though the noop copy does not clobbers the value. It does start a
      new intersecting live range. That means the spillslot register is available for
      use but should not be reused for a two-address instruction modref operand which
      would clobber the new live range.
      
      When we remove the noop copy, update the available information by clearing the
      canClobber bit.
      
      llvm-svn: 32576
      4c306ae0
  9. Dec 08, 2006
  10. Dec 07, 2006
  11. Dec 06, 2006
  12. Dec 01, 2006
  13. Nov 17, 2006
  14. Nov 04, 2006
  15. Nov 02, 2006
  16. Oct 12, 2006
  17. Sep 05, 2006
    • Chris Lattner's avatar
      Fix a long-standing wart in the code generator: two-address instruction lowering · 13a5dcdd
      Chris Lattner authored
      actually *removes* one of the operands, instead of just assigning both operands
      the same register.  This make reasoning about instructions unnecessarily complex,
      because you need to know if you are before or after register allocation to match
      up operand #'s with the target description file.
      
      Changing this also gets rid of a bunch of hacky code in various places.
      
      This patch also includes changes to fold loads into cmp/test instructions in
      the X86 backend, along with a significant simplification to the X86 spill
      folding code.
      
      llvm-svn: 30108
      13a5dcdd
  18. Aug 27, 2006
  19. Aug 25, 2006
    • Chris Lattner's avatar
      Take advantage of the recent improvements to the liveintervals set (tracking · bdf12106
      Chris Lattner authored
      instructions which define each value#) to simplify and improve the coallescer.
      In particular, this patch:
      
      1. Implements iterative coallescing.
      2. Reverts an unsafe hack from handlePhysRegDef, superceeding it with a
         better solution.
      3. Implements PR865, "coallescing" away the second copy in code like:
      
         A = B
         ...
         B = A
      
      This also includes changes to symbolically print registers in intervals
      when possible.
      
      llvm-svn: 29862
      bdf12106
  20. Aug 21, 2006
  21. Jul 21, 2006
  22. Jul 20, 2006
  23. Jun 29, 2006
  24. May 04, 2006
  25. May 02, 2006
  26. May 01, 2006
  27. Apr 30, 2006
  28. Apr 28, 2006
    • Chris Lattner's avatar
      Mapping of physregs can make it so that the designated and input physregs are · 79c50d96
      Chris Lattner authored
      the same.  In this case, don't emit a noop copy.
      
      llvm-svn: 28008
      79c50d96
    • Chris Lattner's avatar
      When we have a two-address instruction where the input cannot be clobbered · 84e95d00
      Chris Lattner authored
      and is already available, instead of falling back to emitting a load, fall
      back to emitting a reg-reg copy.  This generates significantly better code
      for some SSE testcases, as SSE has lots of two-address instructions and
      none of them are read/modify/write.  As one example, this change does:
      
              pshufd %XMM5, XMMWORD PTR [%ESP + 84], 255
              xorps %XMM2, %XMM5
              cmpltps %XMM1, %XMM0
      -       movaps XMMWORD PTR [%ESP + 52], %XMM0
      -       movapd %XMM6, XMMWORD PTR [%ESP + 52]
      +       movaps %XMM6, %XMM0
              cmpltps %XMM6, XMMWORD PTR [%ESP + 68]
              movapd XMMWORD PTR [%ESP + 52], %XMM6
              movaps %XMM6, %XMM0
              cmpltps %XMM6, XMMWORD PTR [%ESP + 36]
              cmpltps %XMM3, %XMM0
      -       movaps XMMWORD PTR [%ESP + 20], %XMM0
      -       movapd %XMM7, XMMWORD PTR [%ESP + 20]
      +       movaps %XMM7, %XMM0
              cmpltps %XMM7, XMMWORD PTR [%ESP + 4]
              movapd XMMWORD PTR [%ESP + 20], %XMM7
              cmpltps %XMM4, %XMM0
      
      ... which is far better than a store followed by a load!
      
      llvm-svn: 28001
      84e95d00
  29. Feb 25, 2006
Loading