6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-01-12 17:32:19 +00:00
Code Issues Projects Releases Wiki Activity

add routines to track the livein/out set for a function

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@21179 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Chris Lattner 2005-04-09 15:22:53 +00:00
parent e00e5ded51
commit dde3a9abc3
1 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
include/llvm/CodeGen/MachineFunction.h
View File

@ -105,6 +105,11 @@ class MachineFunction : private Annotation {
/// for other target specific uses.
bool *UsedPhysRegs;
/// LiveIns/LiveOuts - Keep track of the physical registers that are
/// livein/liveout of the function. Live in values are typically arguments in
/// registers, live out values are typically return values in registers.
std::vector<unsigned> LiveIns, LiveOuts;
public:
MachineFunction(const Function *Fn, const TargetMachine &TM);
~MachineFunction();
@ -167,6 +172,22 @@ public:
/// allocation to keep the PhysRegsUsed array up-to-date.
void changePhyRegUsed(unsigned Reg, bool State) { UsedPhysRegs[Reg] = State; }
// LiveIn/LiveOut management methods.
/// addLiveIn/Out - Add the specified register as a live in/out. Note that it
/// is an error to add the same register to the same set more than once.
void addLiveIn(unsigned Reg) { LiveIns.push_back(Reg); }
void addLiveOut(unsigned Reg) { LiveOuts.push_back(Reg); }
// Iteration support for live in/out sets. These sets are kept in sorted
// order by their register number.
typedef std::vector<unsigned>::const_iterator liveinout_iterator;
liveinout_iterator livein_begin() const { return LiveIns.begin(); }
liveinout_iterator livein_end() const { return LiveIns.end(); }
liveinout_iterator liveout_begin() const { return LiveOuts.begin(); }
liveinout_iterator liveout_end() const { return LiveOuts.end(); }
/// getBlockNumbered - MachineBasicBlocks are automatically numbered when they
/// are inserted into the machine function. The block number for a machine
/// basic block can be found by using the MBB::getBlockNumber method, this