From 73944fb22270697e75408cba52cca276be371a1f Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Sat, 8 Dec 2007 06:39:11 +0000 Subject: refactor some code to avoid overloading the name 'usesLR' in different places to mean different things. Document what the one in PPCFunctionInfo means and when it is valid. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@44699 91177308-0d34-0410-b5e6-96231b3b80d8 --- lib/Target/PowerPC/PPCMachineFunctionInfo.h | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'lib/Target/PowerPC/PPCMachineFunctionInfo.h') diff --git a/lib/Target/PowerPC/PPCMachineFunctionInfo.h b/lib/Target/PowerPC/PPCMachineFunctionInfo.h index e227456e63..bf1fea211b 100644 --- a/lib/Target/PowerPC/PPCMachineFunctionInfo.h +++ b/lib/Target/PowerPC/PPCMachineFunctionInfo.h @@ -39,8 +39,12 @@ public: int getFramePointerSaveIndex() const { return FramePointerSaveIndex; } void setFramePointerSaveIndex(int Idx) { FramePointerSaveIndex = Idx; } + /// UsesLR - This is set when the prolog/epilog inserter does its initial scan + /// of the function, it is true if the LR/LR8 register is ever explicitly + /// accessed/clobbered in the machine function (e.g. by calls and movpctolr, + /// which is used in PIC generation). void setUsesLR(bool U) { UsesLR = U; } - bool usesLR() { return UsesLR; } + bool usesLR() const { return UsesLR; } }; -- cgit v1.2.3