Manage MachineFunctions with an analysis Pass instead of the Annotable

mechanism. To support this, make MachineFunctionPass a little more
complete.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@77654 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Dan Gohman
2009-07-31 01:52:50 +00:00
parent 376cd007ec
commit 933c762371
18 changed files with 187 additions and 136 deletions

View File

@@ -24,19 +24,25 @@
namespace llvm {
// FIXME: This pass should declare that the pass does not invalidate any LLVM
// passes.
struct MachineFunctionPass : public FunctionPass {
/// MachineFunctionPass - This class adapts the FunctionPass interface to
/// allow convenient creation of passes that operate on the MachineFunction
/// representation. Instead of overriding runOnFunction, subclasses
/// override runOnMachineFunction.
class MachineFunctionPass : public FunctionPass {
protected:
explicit MachineFunctionPass(intptr_t ID) : FunctionPass(ID) {}
explicit MachineFunctionPass(void *ID) : FunctionPass(ID) {}
protected:
/// runOnMachineFunction - This method must be overloaded to perform the
/// desired machine code transformation or analysis.
///
virtual bool runOnMachineFunction(MachineFunction &MF) = 0;
public:
/// getAnalysisUsage - Subclasses that override getAnalysisUsage
/// must call this.
virtual void getAnalysisUsage(AnalysisUsage &AU) const;
private:
bool runOnFunction(Function &F);
};