From 6706f3c4b468b2c66dd11d9c0814ffe4a185c738 Mon Sep 17 00:00:00 2001 From: Jim Grosbach Date: Mon, 18 Oct 2010 18:39:46 +0000 Subject: For Thumb2, try to use frame pointer references for stack slots even when a base register is available. rdar://8525298 llvm-svn: 116729 --- llvm/lib/Target/ARM/ARMBaseRegisterInfo.cpp | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) (limited to 'llvm/lib') diff --git a/llvm/lib/Target/ARM/ARMBaseRegisterInfo.cpp b/llvm/lib/Target/ARM/ARMBaseRegisterInfo.cpp index acb61b218ac..37e15f4f1c1 100644 --- a/llvm/lib/Target/ARM/ARMBaseRegisterInfo.cpp +++ b/llvm/lib/Target/ARM/ARMBaseRegisterInfo.cpp @@ -953,8 +953,16 @@ ARMBaseRegisterInfo::ResolveFrameIndexReference(const MachineFunction &MF, return FPOffset; } else if (MFI->hasVarSizedObjects()) { assert(hasBasePointer(MF) && "missing base pointer!"); - // Use the base register since we have it. - FrameReg = BasePtr; + // Try to use the frame pointer if we can, else use the base pointer + // since it's available. This is handy for the emergency spill slot, in + // particular. + if (AFI->isThumb2Function()) { + if (FPOffset >= -255 && FPOffset < 0) { + FrameReg = getFrameRegister(MF); + return FPOffset; + } + } else + FrameReg = BasePtr; } else if (AFI->isThumb2Function()) { // In Thumb2 mode, the negative offset is very limited. Try to avoid // out of range references. -- cgit v1.2.3