Displaying 3 results from an estimated 3 matches for "estimatestacksize".
2010 Mar 29
0
[LLVMdev] Patch - Big stacks on SPU, take 2
On Mar 29, 2010, at 6:50 AM, Kalle Raiskila wrote:
> attached is a second try for the bigstack patch for SPU, with testcase. It is essentially the patch committed as 97091, and reverted as 97099, but with the following additions:
> -in vararg handling, registers are marked to be live, to not confuse the register scavenger
Looks good. You can try running with -verify-machineinstrs to detect
2010 Mar 29
3
[LLVMdev] Patch - Big stacks on SPU, take 2
Hi,
attached is a second try for the bigstack patch for SPU, with testcase. It is
essentially the patch committed as 97091, and reverted as 97099, but with the
following additions:
-in vararg handling, registers are marked to be live, to not confuse the
register scavenger
-function prologue and epilogue are not emitted, if the stack size is 16. 16
means it is empty - there is only the
2012 Oct 22
0
[LLVMdev] register scavenger
...culateFrameObjectOffsets(Fn);
...
if (target needs spill slot) {
call setScavengingFrameIndex and reserve spill slot
calculateFrameObjectOffsets(Fn); // redo calculation.
}
This seems to be simpler and more efficient since you don't need to write
or run a function like ARM's estimateStackSize to estimate the stack size.
Does this sound reasonable or is there something I am missing?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121022/a9853815/attachment.html>