[Support] Update comments about stdout, raw_fd_ostream, and outs()
authorReid Kleckner <rnk@google.com>
Fri, 4 Aug 2017 01:39:23 +0000 (01:39 +0000)
committerReid Kleckner <rnk@google.com>
Fri, 4 Aug 2017 01:39:23 +0000 (01:39 +0000)
commit02aeadcf3d431f35941c628643e919c5aa2169a1
tree97e54bc66abbceab7bb2195eb22dff5ea3353977
parent696e3847dd5723d94335adf65435dc1de229a3b7
[Support] Update comments about stdout, raw_fd_ostream, and outs()

The full story is in the comments:

  // Do not attempt to close stdout or stderr. We used to try to maintain the
  // property that tools that support writing file to stdout should not also
  // write informational output to stdout, but in practice we were never able to
  // maintain this invariant. Many features have been added to LLVM and clang
  // (-fdump-record-layouts, optimization remarks, etc) that print to stdout, so
  // users must simply be aware that mixed output and remarks is a possibility.

NFC, I am just updating comments to reflect reality.

llvm-svn: 310016
llvm/include/llvm/Support/raw_ostream.h
llvm/lib/Support/raw_ostream.cpp