From 633bfa02d6a9a9e414b4118a591c36a11d9a8dcb Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Fri, 7 Sep 2001 21:02:50 +0000 Subject: [PATCH] Remove ReversePostOrderTraversal declaration git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@481 91177308-0d34-0410-b5e6-96231b3b80d8 --- include/llvm/CFGdecls.h | 30 ------------------------------ 1 file changed, 30 deletions(-) diff --git a/include/llvm/CFGdecls.h b/include/llvm/CFGdecls.h index b59a1d25367..fa6d08f526a 100644 --- a/include/llvm/CFGdecls.h +++ b/include/llvm/CFGdecls.h @@ -138,36 +138,6 @@ inline po_const_iterator po_begin(const BasicBlock *BB); inline po_iterator po_end ( BasicBlock *BB); inline po_const_iterator po_end (const BasicBlock *BB); - -//===--------------------------------------------------------------------===// -// Reverse Post Order CFG iterator code -//===--------------------------------------------------------------------===// -// -// This is used to visit basic blocks in a method in reverse post order. This -// class is awkward to use because I don't know a good incremental algorithm to -// computer RPO from a graph. Because of this, the construction of the -// ReversePostOrderTraversal object is expensive (it must walk the entire graph -// with a postorder iterator to build the data structures). The moral of this -// story is: Don't create more ReversePostOrderTraversal classes than neccesary. -// -// This class should be used like this: -// { -// cfg::ReversePostOrderTraversal RPOT(MethodPtr); // Expensive to create -// for (cfg::rpo_iterator I = RPOT.begin(); I != RPOT.end(); ++I) { -// ... -// } -// for (cfg::rpo_iterator I = RPOT.begin(); I != RPOT.end(); ++I) { -// ... -// } -// } -// - -//typedef reverse_iterator::const_iterator> -// rpo_const_iterator; -typedef reverse_iterator::iterator> rpo_iterator; - -class ReversePostOrderTraversal; - } // End namespace cfg #endif -- 2.34.1