Skip to content
  1. Jun 21, 2012
  2. Jun 20, 2012
  3. Jun 09, 2012
  4. Jun 06, 2012
  5. Jun 02, 2012
    • Jakob Stoklund Olesen's avatar
      Switch all register list clients to the new MC*Iterator interface. · 54038d79
      Jakob Stoklund Olesen authored
      No functional change intended.
      
      Sorry for the churn. The iterator classes are supposed to help avoid
      giant commits like this one in the future. The TableGen-produced
      register lists are getting quite large, and it may be necessary to
      change the table representation.
      
      This makes it possible to do so without changing all clients (again).
      
      llvm-svn: 157854
      54038d79
  6. May 12, 2012
  7. Apr 03, 2012
  8. Mar 04, 2012
  9. Jan 11, 2012
  10. Jan 05, 2012
    • Jakob Stoklund Olesen's avatar
      Freeze reserved registers before starting register allocation. · d19d3cab
      Jakob Stoklund Olesen authored
      The register allocators don't currently support adding reserved
      registers while they are running.  Extend the MRI API to keep track of
      the set of reserved registers when register allocation started.
      
      Target hooks like hasFP() and needsStackRealignment() can look at this
      set to avoid reserving more registers during register allocation.
      
      llvm-svn: 147577
      d19d3cab
  11. Aug 11, 2011
  12. Aug 09, 2011
  13. Jul 27, 2011
  14. Jul 02, 2011
  15. Jun 27, 2011
  16. Jun 26, 2011
  17. Jun 03, 2011
  18. May 10, 2011
  19. May 06, 2011
  20. Apr 20, 2011
    • Jakob Stoklund Olesen's avatar
      Prefer cheap registers for busy live ranges. · 0e34c1df
      Jakob Stoklund Olesen authored
      On the x86-64 and thumb2 targets, some registers are more expensive to encode
      than others in the same register class.
      
      Add a CostPerUse field to the TableGen register description, and make it
      available from TRI->getCostPerUse. This represents the cost of a REX prefix or a
      32-bit instruction encoding required by choosing a high register.
      
      Teach the greedy register allocator to prefer cheap registers for busy live
      ranges (as indicated by spill weight).
      
      llvm-svn: 129864
      0e34c1df
  21. Apr 12, 2011
  22. Apr 11, 2011
  23. Apr 05, 2011
  24. Apr 01, 2011
  25. Mar 23, 2011
  26. Mar 16, 2011
  27. Mar 12, 2011
    • Jakob Stoklund Olesen's avatar
      Spill multiple registers at once. · a86595e0
      Jakob Stoklund Olesen authored
      Live range splitting can create a number of small live ranges containing only a
      single real use. Spill these small live ranges along with the large range they
      are connected to with copies. This enables memory operand folding and maximizes
      the spill to fill distance.
      
      Work in progress with known bugs.
      
      llvm-svn: 127529
      a86595e0
  28. Mar 10, 2011
  29. Feb 23, 2011
  30. Feb 18, 2011
  31. Feb 17, 2011
  32. Feb 09, 2011
    • Jakob Stoklund Olesen's avatar
      Evict a lighter single interference before attempting to split a live range. · 1305bc0a
      Jakob Stoklund Olesen authored
      Registers are not allocated strictly in spill weight order when live range
      splitting and spilling has created new shorter intervals with higher spill
      weights.
      
      When one of the new heavy intervals conflicts with a single lighter interval,
      simply evict the old interval instead of trying to split the heavy one.
      
      The lighter interval is a better candidate for splitting, it has a smaller use
      density.
      
      llvm-svn: 125151
      1305bc0a
Loading