Cleanup dump() functions.
We had various variants of defining dump() functions in LLVM. Normalize them (this should just consistently implement the things discussed in http://lists.llvm.org/pipermail/cfe-dev/2014-January/034323.html For reference: - Public headers should just declare the dump() method but not use LLVM_DUMP_METHOD or #if !defined(NDEBUG) || defined(LLVM_ENABLE_DUMP) - The definition of a dump method should look like this: #if !defined(NDEBUG) || defined(LLVM_ENABLE_DUMP) LLVM_DUMP_METHOD void MyClass::dump() { // print stuff to dbgs()... } #endif llvm-svn: 293359
This commit is contained in:
@@ -125,8 +125,9 @@ void CallGraph::print(raw_ostream &OS) const {
|
||||
CN->print(OS);
|
||||
}
|
||||
|
||||
LLVM_DUMP_METHOD
|
||||
void CallGraph::dump() const { print(dbgs()); }
|
||||
#if !defined(NDEBUG) || defined(LLVM_ENABLE_DUMP)
|
||||
LLVM_DUMP_METHOD void CallGraph::dump() const { print(dbgs()); }
|
||||
#endif
|
||||
|
||||
// removeFunctionFromModule - Unlink the function from this module, returning
|
||||
// it. Because this removes the function from the module, the call graph node
|
||||
@@ -194,8 +195,9 @@ void CallGraphNode::print(raw_ostream &OS) const {
|
||||
OS << '\n';
|
||||
}
|
||||
|
||||
LLVM_DUMP_METHOD
|
||||
void CallGraphNode::dump() const { print(dbgs()); }
|
||||
#if !defined(NDEBUG) || defined(LLVM_ENABLE_DUMP)
|
||||
LLVM_DUMP_METHOD void CallGraphNode::dump() const { print(dbgs()); }
|
||||
#endif
|
||||
|
||||
/// removeCallEdgeFor - This method removes the edge in the node for the
|
||||
/// specified call site. Note that this method takes linear time, so it
|
||||
@@ -307,8 +309,10 @@ void CallGraphWrapperPass::print(raw_ostream &OS, const Module *) const {
|
||||
G->print(OS);
|
||||
}
|
||||
|
||||
#if !defined(NDEBUG) || defined(LLVM_ENABLE_DUMP)
|
||||
LLVM_DUMP_METHOD
|
||||
void CallGraphWrapperPass::dump() const { print(dbgs(), nullptr); }
|
||||
#endif
|
||||
|
||||
namespace {
|
||||
struct CallGraphPrinterLegacyPass : public ModulePass {
|
||||
|
||||
Reference in New Issue
Block a user