wangtao
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[AVR] Don't worry about call frame size when initializing frame pointer 

We previously only used the frame pointer if the frame pointer was too
big. This was to work around a bug (described in this old commit)

https://sourceforge.net/p/avr-llvm/code/204/tree//llvm/trunk/AVR/AVRFrameLowering.cpp?diff=50d64d912718465cb887d17a:203

I mistakenly invered the condition assuming it was a typo. I am now
removing it because it doesn't seem to be a problem anymore (plus it's a
dirty hack).

llvm-svn: 283639
This commit is contained in:
Dylan McKay 2016-10-08 01:10:31 +00:00
parent 7c2d41aa9f
commit b16b6d5739
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
llvm/lib/Target/AVR/AVRFrameLowering.cpp
View File

@ -45,10 +45,9 @@ bool AVRFrameLowering::hasReservedCallFrame(const MachineFunction &MF) const {
// conditions: // conditions:
// - Y pointer is reserved to be the frame pointer. // - Y pointer is reserved to be the frame pointer.
// - The function does not contain variable sized objects. // - The function does not contain variable sized objects.
// - MaxCallFrameSize doesn't fit into 6-bits (when it's greater than 63).
const MachineFrameInfo &MFI = MF.getFrameInfo(); const MachineFrameInfo &MFI = MF.getFrameInfo();
return (hasFP(MF) && !MFI.hasVarSizedObjects() && return hasFP(MF) && !MFI.hasVarSizedObjects();
!isUInt<6>(MFI.getMaxCallFrameSize()));
} }
void AVRFrameLowering::emitPrologue(MachineFunction &MF, void AVRFrameLowering::emitPrologue(MachineFunction &MF,