Skip to content
  1. Jan 02, 2014
  2. Jan 01, 2014
  3. Jan 07, 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 04, 2012
  6. Dec 12, 2011
  7. Apr 11, 2011
  8. Nov 18, 2010
  9. Sep 27, 2010
  10. Aug 08, 2010
  11. Jul 30, 2010
    • Duncan Sands's avatar
      Fix the ValueMap copy constructor. The issue is that the map keys are value · cb59bfa7
      Duncan Sands authored
      handles with a pointer to the containing map.  When a map is copied, these
      pointers need to be corrected to point to the new map.  If not, then consider
      the case of a map M1 which maps a value V to something.  Create a copy M2 of
      M1.  At this point there are two value handles on V, one representing V as a
      key in M1, the other representing V as a key in M2.  But both value handles
      point to M1 as the containing map.  Now delete V.  The value handles remove
      themselves from their containing map (which destroys them), but only the first
      value handle is successful: the second one cannot remove itself from M1 as
      (once the first one has removed itself) there is nothing there to remove; it
      is therefore not destroyed.  This causes an assertion failure "All references
      to V were not removed?".
      
      llvm-svn: 109851
      cb59bfa7
  12. Jul 10, 2010
  13. Apr 18, 2010
  14. Nov 19, 2009
  15. Oct 27, 2009
  16. Oct 23, 2009
  17. Oct 22, 2009
Loading