Skip to content
  1. Dec 21, 2012
  2. 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
  3. Jun 25, 2012
  4. Dec 14, 2011
  5. Nov 01, 2011
  6. Sep 14, 2011
  7. Apr 22, 2011
  8. Apr 04, 2011
    • Eric Christopher's avatar
      Assorted bugfixes in object file handling: · ee066fc4
      Eric Christopher authored
       - Adds support for sniffing PE/COFF files on win32 (.exe and .dll)
         which are COFF files that have an MS-DOS compatibility stub on
         the front of them.
      
       - Fixes a bug in the COFFObjectFile's support for the Microsoft COFF
         extension for long symbol names, wherein it was attempting to parse
         the leading '/' in an extended symbol name reference as part of the
         integer offset.
      
       - Fixes bugs in COFFObjectFile and ELFObjectFile wherein section
         and symbol iterators were being returned with uninitialized bytes;
         the type DataRefImpl is a union between 2 32-bit words (d.a and d.b)
         and a single intptr_t word (p). Only p was being initialized, so in
         32-bit builds the result would be iterators with random upper 32-bit
         words in their DataRefImpls. This caused random failures when
         seeking around in object files.
      
      Patch by Graydon Hoare!
      
      llvm-svn: 128799
      ee066fc4
  9. Jan 15, 2011
  10. Jan 10, 2011
  11. Dec 28, 2010
  12. Dec 01, 2010
  13. Nov 29, 2010
  14. Nov 17, 2010
  15. Nov 02, 2010
  16. Sep 16, 2010
  17. Aug 31, 2010
  18. May 27, 2010
  19. Dec 17, 2009
  20. Oct 25, 2009
  21. Aug 24, 2009
    • Chris Lattner's avatar
      Prune #includes from llvm/Linker.h and llvm/System/Path.h, · c521f541
      Chris Lattner authored
      forcing them down into various .cpp files.
      
      This change also:
      1. Renames TimeValue::toString() and Path::toString() to ::str()
         for similarity with the STL.
      2. Removes all stream insertion support for sys::Path, forcing
         clients to call .str().
      3. Removes a use of Config/alloca.h from bugpoint, using smallvector
         instead.
      4. Weans llvm-db off <iostream>
      
      sys::Path really needs to be gutted, but I don't have the desire to
      do it at this point.
      
      llvm-svn: 79869
      c521f541
  22. Jul 12, 2009
  23. Apr 25, 2009
    • Torok Edwin's avatar
      Fix g++-4.4.0 warning, it was causing llvm-nm to fail on wrapped BC files: · c8afb09a
      Torok Edwin authored
      Path.cpp:59: warning: case label value exceeds maximum value for type
      magic[0] is a (signed) char, but some case values are unsigned (e.g. 0xde).
      When magic[0] was 0xde, the switch has taken the default branch instead of case
      0xde branch.
      Apparently this was the behaviour with older versions of gcc too, but not with g++.
      Now g++-4.4 behaves as gcc, and ignores unsigned case values out of range signed
      range.
      
      llvm-svn: 70038
      c8afb09a
  24. Apr 09, 2009
  25. Jul 22, 2008
  26. Jul 09, 2008
    • Chris Lattner's avatar
      Add a little wrapper header that is put around bc files when emitting · a660f4bb
      Chris Lattner authored
      bc files for modules with a target triple that indicates they are for
      darwin.  The reader unconditionally handles this, and the writer could
      turn this on for more targets if we care.
      
      This change has two benefits for darwin:
      
      1) it allows us to encode the cpu type of the file in an easy to read
         place that doesn't require decoding the bc file.
      2) it works around a bug (IMO) in darwin's AR where it is incapable of
         handling files that are not a multiple of 8 bytes long.  BC files
         are only guaranteed to be multiples of 4 bytes long.
      
      llvm-svn: 53275
      a660f4bb
  27. Jun 26, 2008
  28. Jun 15, 2008
  29. May 21, 2008
  30. May 05, 2008
  31. Apr 08, 2008
  32. Apr 07, 2008
  33. Feb 27, 2008
  34. Feb 20, 2008
  35. Jan 09, 2008
  36. Dec 29, 2007
Loading