Skip to content
  1. Jun 24, 2011
    • Evan Cheng's avatar
      Starting to refactor Target to separate out code that's needed to fully describe · 24753317
      Evan Cheng authored
      target machine from those that are only needed by codegen. The goal is to
      sink the essential target description into MC layer so we can start building
      MC based tools without needing to link in the entire codegen.
      
      First step is to refactor TargetRegisterInfo. This patch added a base class
      MCRegisterInfo which TargetRegisterInfo is derived from. Changed TableGen to
      separate register description from the rest of the stuff.
      
      llvm-svn: 133782
      24753317
  2. Jun 16, 2011
    • Jakob Stoklund Olesen's avatar
      Use set operations instead of plain lists to enumerate register classes. · 99f35eab
      Jakob Stoklund Olesen authored
      This simplifies many of the target description files since it is common
      for register classes to be related or contain sequences of numbered
      registers.
      
      I have verified that this doesn't change the files generated by TableGen
      for ARM and X86. It alters the allocation order of MBlaze GPR and Mips
      FGR32 registers, but I believe the change is benign.
      
      llvm-svn: 133105
      99f35eab
  3. Jun 09, 2011
    • Jakob Stoklund Olesen's avatar
      Remove custom allocation order boilerplate that is no longer needed. · 5750ca70
      Jakob Stoklund Olesen authored
      The register allocators automatically filter out reserved registers and
      place the callee saved registers last in the allocation order, so custom
      methods are no longer necessary just for that.
      
      Some targets still use custom allocation orders:
      
      ARM/Thumb: The high registers are removed from GPR in thumb mode. The
      NEON allocation orders prefer to use non-VFP2 registers first.
      
      X86: The GR8 classes omit AH-DH in x86-64 mode to avoid REX trouble.
      
      SystemZ: Some of the allocation orders are omitting R12 aliases without
      explanation. I don't understand this target well enough to fix that. It
      looks like all the boilerplate could be removed by reserving the right
      registers.
      
      llvm-svn: 132781
      5750ca70
    • Eric Christopher's avatar
      Add a parameter to CCState so that it can access the MachineFunction. · 0713a9d8
      Eric Christopher authored
      No functional change.
      
      Part of PR6965
      
      llvm-svn: 132763
      0713a9d8
  4. May 30, 2011
  5. May 29, 2011
  6. May 06, 2011
  7. May 03, 2011
  8. Apr 15, 2011
  9. Feb 22, 2011
    • Devang Patel's avatar
      Revert r124611 - "Keep track of incoming argument's location while emitting LiveIns." · f3292b21
      Devang Patel authored
      In other words, do not keep track of argument's location.  The debugger (gdb) is not prepared to see line table entries for arguments. For the debugger, "second" line table entry marks beginning of function body.
      This requires some coordination with debugger to get this working. 
       - The debugger needs to be aware of prolog_end attribute attached with line table entries.
       - The compiler needs to accurately mark prolog_end in line table entries (at -O0 and at -O1+)
      
      llvm-svn: 126155
      f3292b21
  10. Feb 21, 2011
  11. Feb 20, 2011
  12. Feb 16, 2011
  13. Feb 12, 2011
  14. Jan 31, 2011
  15. Jan 22, 2011
  16. Jan 21, 2011
  17. Jan 20, 2011
  18. Jan 18, 2011
  19. Jan 16, 2011
  20. Jan 13, 2011
  21. Jan 12, 2011
  22. Jan 11, 2011
  23. Jan 10, 2011
  24. Dec 29, 2010
  25. Dec 28, 2010
    • Venkatraman Govindaraju's avatar
      · 2f15503d
      Venkatraman Govindaraju authored
      Multiple SPARC backend fixes: added Y register; updated select_cc, subx, subxcc defs/uses; 
      and fixed CustomInserter.
      
      llvm-svn: 122607
      2f15503d
  26. Dec 23, 2010
  27. Dec 21, 2010
  28. Nov 23, 2010
  29. Nov 18, 2010
  30. Nov 15, 2010
  31. Nov 14, 2010
  32. Nov 03, 2010
    • Duncan Sands's avatar
      Inside the calling convention logic LocVT is always a simple · f5dda01f
      Duncan Sands authored
      value type, so there is no point in passing it around using
      an EVT.  Use the simpler MVT everywhere.  Rather than trying
      to propagate this information maximally in all the code that
      using the calling convention stuff, I chose to do a mainly
      low impact change instead.
      
      llvm-svn: 118167
      f5dda01f
  33. Sep 29, 2010
Loading