Skip to content
  1. Oct 31, 2006
    • Anton Korobeynikov's avatar
      1. Clean up code due to changes in SwitchTo*Section(2) · aa4c0f93
      Anton Korobeynikov authored
      2. Added partial debug support for mingw\cygwin targets (the same as
         Linux\ELF). Please note, that currently mingw\cygwin uses 'stabs' format
         for storing debug info by default, thus many (runtime) libraries has
         this information included. These formats shouldn't be mixed in one binary
         ('stabs' & 'DWARF'), otherwise binutils tools will be confused.
      
      llvm-svn: 31311
      aa4c0f93
  2. Oct 24, 2006
  3. Oct 20, 2006
    • Reid Spencer's avatar
      For PR950: · e0fc4dfc
      Reid Spencer authored
      This patch implements the first increment for the Signless Types feature.
      All changes pertain to removing the ConstantSInt and ConstantUInt classes
      in favor of just using ConstantInt.
      
      llvm-svn: 31063
      e0fc4dfc
  4. Oct 05, 2006
  5. Sep 26, 2006
  6. Sep 21, 2006
  7. Sep 14, 2006
  8. Sep 08, 2006
  9. Sep 06, 2006
  10. Jun 01, 2006
  11. May 26, 2006
  12. May 16, 2006
  13. May 09, 2006
  14. May 08, 2006
    • Evan Cheng's avatar
      Fixing truncate. Previously we were emitting truncate from r16 to r8 as · 9733bde7
      Evan Cheng authored
      movw. That is we promote the destination operand to r16. So
              %CH = TRUNC_R16_R8 %BP
      is emitted as
              movw %bp, %cx.
      
      This is incorrect. If %cl is live, it would be clobbered.
      Ideally we want to do the opposite, that is emitted it as
              movb ??, %ch
      But this is not possible since %bp does not have a r8 sub-register.
      
      We are now defining a new register class R16_ which is a subclass of R16
      containing only those 16-bit registers that have r8 sub-registers (i.e.
      AX - DX). We isel the truncate to two instructions, a MOV16to16_ to copy the
      value to the R16_ class, followed by a TRUNC_R16_R8.
      
      Due to bug 770, the register colaescer is not going to coalesce between R16 and
      R16_. That will be fixed later so we can eliminate the MOV16to16_. Right now, it
      can only be eliminated if we are lucky that source and destination registers are
      the same.
      
      llvm-svn: 28164
      9733bde7
  15. May 06, 2006
  16. May 05, 2006
  17. May 04, 2006
  18. May 02, 2006
  19. May 01, 2006
  20. Apr 29, 2006
  21. Apr 28, 2006
  22. Apr 22, 2006
  23. Apr 07, 2006
  24. Mar 23, 2006
  25. Mar 14, 2006
Loading