From 5bc6d0fbe4fe03fe1a9f7bc2aead08c233e9e885 Mon Sep 17 00:00:00 2001 From: Reid Kleckner Date: Fri, 8 Nov 2013 21:28:00 +0000 Subject: Make -fdump-vtable-layouts print to stdout, not stderr This makes it consistent with -fdump-record-layouts, which was moved to outs() in r186219. My reasoning for going with stdout is that when one of these options is present, the layouts are really a program output, and shouldn't be interleaved with diagnostics, which are on stderr. Reviewers: timurrrr Differential Revision: http://llvm-reviews.chandlerc.com/D2127 llvm-svn: 194279 --- clang/lib/AST/VTableBuilder.cpp | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'clang/lib/AST/VTableBuilder.cpp') diff --git a/clang/lib/AST/VTableBuilder.cpp b/clang/lib/AST/VTableBuilder.cpp index fd768d81260..5f7ae0f3ff4 100644 --- a/clang/lib/AST/VTableBuilder.cpp +++ b/clang/lib/AST/VTableBuilder.cpp @@ -997,7 +997,7 @@ public: LayoutVTable(); if (Context.getLangOpts().DumpVTableLayouts) - dumpLayout(llvm::errs()); + dumpLayout(llvm::outs()); } uint64_t getNumThunks() const { @@ -2596,7 +2596,7 @@ public: LayoutVFTable(); if (Context.getLangOpts().DumpVTableLayouts) - dumpLayout(llvm::errs()); + dumpLayout(llvm::outs()); } uint64_t getNumThunks() const { return Thunks.size(); } @@ -3292,7 +3292,7 @@ void MicrosoftVTableContext::computeVTableRelatedInformation( MethodVFTableLocations.insert(NewMethodLocations.begin(), NewMethodLocations.end()); if (Context.getLangOpts().DumpVTableLayouts) - dumpMethodLocations(RD, NewMethodLocations, llvm::errs()); + dumpMethodLocations(RD, NewMethodLocations, llvm::outs()); } void MicrosoftVTableContext::dumpMethodLocations( -- cgit v1.2.3