Skip to content
  1. Oct 20, 2009
  2. Oct 10, 2009
    • Dan Gohman's avatar
      Factor out LiveIntervalAnalysis' code to determine whether an instruction · 87b02d5b
      Dan Gohman authored
      is trivially rematerializable and integrate it into
      TargetInstrInfo::isTriviallyReMaterializable. This way, all places that
      need to know whether an instruction is rematerializable will get the
      same answer.
      
      This enables the useful parts of the aggressive-remat option by
      default -- using AliasAnalysis to determine whether a memory location
      is invariant, and removes the questionable parts -- rematting operations
      with virtual register inputs that may not be live everywhere.
      
      llvm-svn: 83687
      87b02d5b
  3. Oct 09, 2009
  4. Oct 07, 2009
  5. Oct 03, 2009
  6. Sep 26, 2009
  7. Sep 25, 2009
    • Dan Gohman's avatar
      Improve MachineMemOperand handling. · 48b185d6
      Dan Gohman authored
       - Allocate MachineMemOperands and MachineMemOperand lists in MachineFunctions.
         This eliminates MachineInstr's std::list member and allows the data to be
         created by isel and live for the remainder of codegen, avoiding a lot of
         copying and unnecessary translation. This also shrinks MemSDNode.
       - Delete MemOperandSDNode. Introduce MachineSDNode which has dedicated
         fields for MachineMemOperands.
       - Change MemSDNode to have a MachineMemOperand member instead of its own
         fields with the same information. This introduces some redundancy, but
         it's more consistent with what MachineInstr will eventually want.
       - Ignore alignment when searching for redundant loads for CSE, but remember
         the greatest alignment.
      
      Target-specific code which previously used MemOperandSDNodes with generic
      SDNodes now use MemIntrinsicSDNodes, with opcodes in a designated range
      so that the SelectionDAG framework knows that MachineMemOperand information
      is available.
      
      llvm-svn: 82794
      48b185d6
  8. Sep 23, 2009
  9. Sep 21, 2009
  10. Sep 20, 2009
    • Dale Johannesen's avatar
      When computing live intervals for earlyclobber operands, · a894053a
      Dale Johannesen authored
      we pushed the beginning of the interval back 1, so the
      interval would overlap with inputs that die.  We were
      also pushing the end of the interval back 1, though,
      which means the earlyclobber didn't overlap with other
      output operands.  Don't do this.  PR 4964.
      
      llvm-svn: 82342
      a894053a
  11. Sep 15, 2009
  12. Sep 14, 2009
    • Evan Cheng's avatar
      Add early coalescing to liveintervals. This is work in progress and is known... · 7f789596
      Evan Cheng authored
      Add early coalescing to liveintervals. This is work in progress and is known to miscompute some tests. Read it at your own rish, I have aged 10 year while writing this.
      
      The gist of this is if source of some of the copies that feed into a phi join is defined by the phi join, we'd like to eliminate them. However, if any of the non-identity source overlaps the live interval of the phi join then the coalescer won't be able to coalesce them. The early coalescer's job is to eliminate the identity copies by partially-coalescing the two live intervals.
      
      llvm-svn: 81796
      7f789596
  13. Sep 12, 2009
  14. Sep 04, 2009
  15. Aug 23, 2009
  16. Aug 22, 2009
  17. Aug 11, 2009
  18. Aug 05, 2009
  19. Aug 03, 2009
    • David Greene's avatar
      · ec9bc288
      David Greene authored
      Re-apply LiveInterval index dumping patch, with fixes suggested by Bill
      and others.
      
      llvm-svn: 78003
      ec9bc288
  20. Aug 01, 2009
  21. Jul 25, 2009
    • Daniel Dunbar's avatar
      More migration to raw_ostream, the water has dried up around the iostream hole. · 0dd5e1ed
      Daniel Dunbar authored
       - Some clients which used DOUT have moved to DEBUG. We are deprecating the
         "magic" DOUT behavior which avoided calling printing functions when the
         statement was disabled. In addition to being unnecessary magic, it had the
         downside of leaving code in -Asserts builds, and of hiding potentially
         unnecessary computations.
      
      llvm-svn: 77019
      0dd5e1ed
  22. Jul 24, 2009
  23. Jul 22, 2009
    • David Greene's avatar
      · e88680e3
      David Greene authored
      Constify the key in Mi2IndexMap.
      
      llvm-svn: 76801
      e88680e3
  24. Jul 21, 2009
    • Chris Lattner's avatar
      revert r76602, 76603, and r76615, pending design discussions. · 1eede6c6
      Chris Lattner authored
      llvm-svn: 76646
      1eede6c6
    • David Greene's avatar
      · ef1f36d3
      David Greene authored
      Prefix IR dumps with LiveInterval indices when possible.  This turns
      this:
      
      	%ESI<def> = MOV32rr %EDI<kill>
      	ADJCALLSTACKDOWN64 0, %RSP<imp-def>, %EFLAGS<imp-def,dead>, %RSP<imp-use>
      	%reg1027<def> = MOVZX64rr32 %ESI
      	%reg1027<def> = ADD64ri8 %reg1027, 15, %EFLAGS<imp-def,dead>
      	%reg1027<def> = AND64ri8 %reg1027, -16, %EFLAGS<imp-def,dead>
      	%RDI<def> = MOV64rr %RSP
      	%RDI<def> = SUB64rr %RDI, %reg1027<kill>, %EFLAGS<imp-def,dead>
      	%RSP<def> = MOV64rr %RDI
      
      into this:
      
      4	%reg1024<def> = MOV32rr %EDI<kill>
      12	ADJCALLSTACKDOWN64 0, %RSP<imp-def>, %EFLAGS<imp-def,dead>, %RSP<imp-use>
      20	%reg1025<def> = MOVZX64rr32 %reg1024
      28	%reg1026<def> = MOV64rr %reg1025<kill>
      36	%reg1026<def> = ADD64ri8 %reg1026, 15, %EFLAGS<imp-def,dead>
      44	%reg1027<def> = MOV64rr %reg1026<kill>
      52	%reg1027<def> = AND64ri8 %reg1027, -16, %EFLAGS<imp-def,dead>
      60	%reg1028<def> = MOV64rr %RSP
      68	%reg1029<def> = MOV64rr %reg1028<kill>
      76	%reg1029<def> = SUB64rr %reg1029, %reg1027<kill>, %EFLAGS<imp-def,dead>
      84	%RSP<def> = MOV64rr %reg1029
      
      This helps greatly when debugging register allocation and coalescing
      problems.
      
      llvm-svn: 76615
      ef1f36d3
  25. Jul 17, 2009
  26. Jul 16, 2009
  27. Jul 14, 2009
  28. Jul 11, 2009
  29. Jul 10, 2009
  30. Jul 09, 2009
    • Lang Hames's avatar
      Improved tracking of value number kills. VN kills are now represented · dab7b06d
      Lang Hames authored
      as an (index,bool) pair. The bool flag records whether the kill is a
      PHI kill or not. This code will be used to enable splitting of live
      intervals containing PHI-kills.
      
      A slight change to live interval weights introduced an extra spill
      into lsr-code-insertion (outside the critical sections). The test 
      condition has been updated to reflect this.
      
      llvm-svn: 75097
      dab7b06d
Loading