Skip to content
  1. Oct 17, 2009
  2. Sep 15, 2009
  3. Sep 11, 2009
    • Dan Gohman's avatar
      Fix llvm-extract's "writing bitcode to a terminal" warning, which wasn't · e5929236
      Dan Gohman authored
      working. To support this, add an is_displayed() function to raw_ostream,
      and generalize Process::StandardOutIsDisplayed and friends in order to
      support it.
      
      Also, call RemoveFileOnSignal before creating a file instead of after, so
      that the file isn't left behind if the program is interrupted between when
      the file is created and RemoveFileOnSignal is called.
      
      While here, add a -S to llvm-extract and port it to IRReader so that it
      supports assembly input.
      
      llvm-svn: 81568
      e5929236
  4. Aug 25, 2009
    • Dan Gohman's avatar
      Make LLVM command-line tools overwrite their output files without -f. · 61a8796d
      Dan Gohman authored
      This is conventional command-line tool behavior. -f now just means
      "enable binary output on terminals".
      
      Add a -f option to llvm-extract and llvm-link, for consistency.
      
      Remove F_Force from raw_fd_ostream and enable overwriting and
      truncating by default. Introduce an F_Excl flag to permit users to
      enable a failure when the file already exists. This flag is
      currently unused.
      
      Update Makefiles and documentation accordingly.
      
      llvm-svn: 79990
      61a8796d
  5. Aug 24, 2009
  6. Aug 23, 2009
    • Daniel Dunbar's avatar
      Fix off-by-one in llvm::Format::print. · 47a309c5
      Daniel Dunbar authored
       - This also shortens the Format.h implementation, and uses the print buffer
         fully (it was wasting a character).
      
       - This manifested as llvm-test failures, because one side effect was that
         raw_ostream would write garbage '\x00' values into the output stream if it
         happened that the string was at the end of the buffer. This meant that grep
         would report 'Binary file matches', which meant the silly pattern matching
         llvm-test eventually does would fail. Cute. :)
      
      llvm-svn: 79862
      47a309c5
    • Benjamin Kramer's avatar
      Fix windows build. · b451afb5
      Benjamin Kramer authored
      llvm-svn: 79845
      b451afb5
    • Chris Lattner's avatar
      Change raw_fd_ostream to take flags as an optional bitmask · 9e6f1f16
      Chris Lattner authored
      instead of as two bools.  Use this to add a F_Append flag
      which has the obvious behavior.
      
      Other unrelated changes conflated into this patch:
      
      1. REmove EH stuff from llvm-dis and llvm-as, the try blocks
         are dead.
      2. Simplify the filename inference code in llvm-as/llvm-dis,
         because raw_fd_ostream does the right thing with '-'.
      3. Switch machine verifier to use raw_ostream instead of ostream
         (Which is the thing that needed append in the first place).
      
      llvm-svn: 79807
      9e6f1f16
    • Chris Lattner's avatar
      add a raw_ostream::indent method, to be used like: · e6db2c33
      Chris Lattner authored
        OS.indent(i) << "whatever";
      
      people seem to like indenting things ;-)
      
      llvm-svn: 79784
      e6db2c33
  7. Aug 19, 2009
  8. Aug 18, 2009
  9. Aug 15, 2009
  10. Aug 14, 2009
  11. Aug 13, 2009
  12. Jul 30, 2009
  13. Jul 29, 2009
  14. Jul 27, 2009
  15. Jul 16, 2009
    • Daniel Dunbar's avatar
      Add raw_null_ostream and llvm::nulls(), a raw_ostream that discards output. · 95a551ad
      Daniel Dunbar authored
       - No functionality change.
      
      llvm-svn: 76103
      95a551ad
    • Dan Gohman's avatar
      Use size_t. · f199ad6e
      Dan Gohman authored
      llvm-svn: 76069
      f199ad6e
    • Dan Gohman's avatar
      Change raw_ostream so that it doesn't call llvm_report_error · 58fcef91
      Dan Gohman authored
      immediately on every output error. Instead, add a flag to
      raw_ostream, and set the flag whenever an error is detected.
      
      The flag can be queried and cleared from the public API. This
      gives applications more flexibility to handling errors in
      application-specific ways.
      
      If the flag is not cleared when the raw_ostream is destructed,
      llvm_report_error is called from the destructor. This ensures
      that errors are not implicitly silenced, and provides
      convenient default behavior for tools like llc and opt.
      Clients wishing to avoid llvm_report_error calls from
      raw_ostream should check for errors and clear the error flag.
      
      llvm-svn: 75857
      58fcef91
  16. Jul 15, 2009
Loading