Skip to content
  1. Sep 20, 2013
  2. Sep 11, 2013
  3. Sep 10, 2013
    • Rui Ueyama's avatar
      Try to unbreak mingw32 buildbot. · 754a3ead
      Rui Ueyama authored
      llvm-svn: 190438
      754a3ead
    • Rui Ueyama's avatar
      Add getenv() wrapper that works on multibyte environment variable. · 471d0c57
      Rui Ueyama authored
      On Windows, character encoding of multibyte environment variable varies
      depending on settings. The only reliable way to handle it I think is to use
      GetEnvironmentVariableW().
      
      GetEnvironmentVariableW() works on wchar_t string, which is on Windows UTF16
      string. That's not ideal because we use UTF-8 as the internal encoding in LLVM.
      This patch defines a wrapper function which takes and returns UTF-8 string for
      GetEnvironmentVariableW().
      
      The wrapper function does not do any conversion and just forwards the argument
      to getenv() on Unix.
      
      Differential Revision: http://llvm-reviews.chandlerc.com/D1612
      
      llvm-svn: 190423
      471d0c57
  4. Sep 09, 2013
    • Bob Wilson's avatar
      Update CMake file to fix buildbots. · 6b28b318
      Bob Wilson authored
      llvm-svn: 190331
      6b28b318
    • Bob Wilson's avatar
      Revert patches to add case-range support for PR1255. · e407736a
      Bob Wilson authored
      The work on this project was left in an unfinished and inconsistent state.
      Hopefully someone will eventually get a chance to implement this feature, but
      in the meantime, it is better to put things back the way the were.  I have
      left support in the bitcode reader to handle the case-range bitcode format,
      so that we do not lose bitcode compatibility with the llvm 3.3 release.
      
      This reverts the following commits: 155464, 156374, 156377, 156613, 156704,
      156757, 156804 156808, 156985, 157046, 157112, 157183, 157315, 157384, 157575,
      157576, 157586, 157612, 157810, 157814, 157815, 157880, 157881, 157882, 157884,
      157887, 157901, 158979, 157987, 157989, 158986, 158997, 159076, 159101, 159100,
      159200, 159201, 159207, 159527, 159532, 159540, 159583, 159618, 159658, 159659,
      159660, 159661, 159703, 159704, 160076, 167356, 172025, 186736
      
      llvm-svn: 190328
      e407736a
  5. Sep 04, 2013
  6. Aug 22, 2013
  7. Aug 16, 2013
  8. Aug 14, 2013
  9. Aug 12, 2013
  10. Aug 08, 2013
  11. Aug 07, 2013
  12. Aug 05, 2013
  13. Aug 01, 2013
  14. Jul 31, 2013
  15. Jul 30, 2013
  16. Jul 29, 2013
  17. Jul 25, 2013
  18. Jul 23, 2013
    • Eli Bendersky's avatar
      Refactor the unit test for MemoryBuffer::getOpenFileSlice · bb506fce
      Eli Bendersky authored
      Run in two different modes: with and without reopening the temporary file
      between creating it and mapping it with MemoryBuffer.
      
      llvm-svn: 186986
      bb506fce
    • Rafael Espindola's avatar
      Split getOpenFile into getOpenFile and getOpenFileSlice. · 3d2ac2e4
      Rafael Espindola authored
      The main observation is that we never need both the filesize and the map size.
      When mapping a slice of a file, it doesn't make sense to request a null
      terminator and that would be the only case where the filesize would be used.
      
      There are other cleanups that should be done in this area:
      
      * A client should not have to pass the size (even an explicit -1) to say if
        it wants a null terminator or not, so we should probably swap the argument
        order.
      * The default should be to not require a null terminator. Very few clients
        require this, but many end up asking for it just because it is the default.
      
      llvm-svn: 186984
      3d2ac2e4
    • Eli Bendersky's avatar
      Add a simple unit test for MemoryBuffer::getOpenFile · f288626c
      Eli Bendersky authored
      llvm-svn: 186887
      f288626c
  19. Jul 19, 2013
  20. Jul 18, 2013
Loading