Skip to content
  1. Jul 21, 2013
  2. Jun 28, 2013
  3. May 25, 2013
  4. Jan 02, 2013
    • Chandler Carruth's avatar
      Move all of the header files which are involved in modelling the LLVM IR · 9fb823bb
      Chandler Carruth authored
      into their new header subdirectory: include/llvm/IR. This matches the
      directory structure of lib, and begins to correct a long standing point
      of file layout clutter in LLVM.
      
      There are still more header files to move here, but I wanted to handle
      them in separate commits to make tracking what files make sense at each
      layer easier.
      
      The only really questionable files here are the target intrinsic
      tablegen files. But that's a battle I'd rather not fight today.
      
      I've updated both CMake and Makefile build systems (I think, and my
      tests think, but I may have missed something).
      
      I've also re-sorted the includes throughout the project. I'll be
      committing updates to Clang, DragonEgg, and Polly momentarily.
      
      llvm-svn: 171366
      9fb823bb
  5. Dec 03, 2012
    • Chandler Carruth's avatar
      Use the new script to sort the includes of every file under lib. · ed0881b2
      Chandler Carruth authored
      Sooooo many of these had incorrect or strange main module includes.
      I have manually inspected all of these, and fixed the main module
      include to be the nearest plausible thing I could find. If you own or
      care about any of these source files, I encourage you to take some time
      and check that these edits were sensible. I can't have broken anything
      (I strictly added headers, and reordered them, never removed), but they
      may not be the headers you'd really like to identify as containing the
      API being implemented.
      
      Many forward declarations and missing includes were added to a header
      files to allow them to parse cleanly when included first. The main
      module rule does in fact have its merits. =]
      
      llvm-svn: 169131
      ed0881b2
  6. Nov 21, 2012
  7. Sep 27, 2012
  8. Sep 17, 2012
  9. Sep 12, 2012
  10. Sep 06, 2012
  11. Aug 01, 2012
  12. Jun 02, 2012
  13. Mar 27, 2012
  14. Mar 17, 2012
  15. Mar 09, 2012
  16. Feb 25, 2012
    • NAKAMURA Takumi's avatar
      Target/X86: Fix assertion failures and warnings caused by r151382 _ftol2... · bdf94879
      NAKAMURA Takumi authored
      Target/X86: Fix assertion failures and warnings caused by r151382 _ftol2 lowering for i386-*-win32 targets. Patch by Joe Groff.
      
      [Joe Groff] Hi everyone. My previous patch applied as r151382 had a few problems:
      Clang raised a warning, and X86 LowerOperation would assert out for
      fptoui f64 to i32 because it improperly lowered to an illegal
      BUILD_PAIR. Here's a patch that addresses these issues. Let me know if
      any other changes are necessary. Thanks.
      
      llvm-svn: 151432
      bdf94879
  17. Feb 24, 2012
  18. Aug 12, 2011
  19. Aug 08, 2011
    • Jakob Stoklund Olesen's avatar
      Don't clobber pending ST regs when FP regs are killed. · 4f0ace56
      Jakob Stoklund Olesen authored
      X86FloatingPoint keeps track of pending ST registers for an upcoming
      inline asm instruction with fixed stack register constraints.  It does
      this by remembering which FP register holds the value that should appear
      at a fixed stack position for the inline asm.
      
      When that FP register is killed before the inline asm, make sure to
      duplicate it to a scratch register, so the ST register still has a live
      FP reference.
      
      This could happen when the same FP register was copied to two ST
      registers, or when a spill instruction is inserted between the ST copy
      and the inline asm.
      
      This fixes PR10602.
      
      llvm-svn: 137050
      4f0ace56
  20. Aug 03, 2011
  21. Jul 02, 2011
  22. Jun 30, 2011
  23. Jun 28, 2011
    • Jakob Stoklund Olesen's avatar
      Clean up the handling of the x87 fp stack to make it more robust. · 7297e7e2
      Jakob Stoklund Olesen authored
      Drop the FpMov instructions, use plain COPY instead.
      
      Drop the FpSET/GET instruction for accessing fixed stack positions.
      Instead use normal COPY to/from ST registers around inline assembly, and
      provide a single new FpPOP_RETVAL instruction that can access the return
      value(s) from a call. This is still necessary since you cannot tell from
      the CALL instruction alone if it returns anything on the FP stack. Teach
      fast isel to use this.
      
      This provides a much more robust way of handling fixed stack registers -
      we can tolerate arbitrary FP stack instructions inserted around calls
      and inline assembly. Live range splitting could sometimes break x87 code
      by inserting spill code in unfortunate places.
      
      As a bonus we handle floating point inline assembly correctly now.
      
      llvm-svn: 134018
      7297e7e2
  24. Jun 27, 2011
  25. Apr 15, 2011
  26. Jan 04, 2011
  27. Oct 23, 2010
  28. Oct 21, 2010
  29. Oct 13, 2010
  30. Aug 18, 2010
  31. Aug 16, 2010
  32. Aug 06, 2010
Loading