Displaying 3 results from an estimated 3 matches for "pr768".
2006 May 23
0
[LLVMdev] Spilling register and frame indices
...+ offset
> [virtual_register]
>
> and then have 'virtual_register' allocated on next iteration of register
> allocator?
This is one approach. Another approach is to have to spiller scavange
registers, which is the subject of this enhancement request:
http://llvm.org/PR768
> Also, while RegAllocLocal and RegAllocSimple directly call
> storeRegToStackSlot, I would not found any calls to that method in
> RegAllocLinearScan. Am I missing something?
RegAllocLinearScan just does register assignment, then the code in
VirtRegMap.cpp (poorly named) actually takes...
2006 May 23
4
[LLVMdev] Spilling register and frame indices
Hi,
right now, LLVM does register spilling by:
1. Creating stack object
2. Passing index of that stack object to MRegisterInfo::storeRegToStackSlot
3. At later stage, frame indices are replaced by calling to
MRegisterInfo::eliminateFrameIndex.
This works for me, but there's slight problem. The target does not have
"register + contant" addressing mode, so accessing frame index
2006 May 24
1
[LLVMdev] Re: Spilling register and frame indices
...ris Lattner wrote:
>> and then have 'virtual_register' allocated on next iteration of register
>> allocator?
>
> This is one approach. Another approach is to have to spiller scavange
> registers, which is the subject of this enhancement request:
> http://llvm.org/PR768
Can you given some references for this "scavange" thing? Google and
ResearchIndex are silent on the topic.
>> Also, while RegAllocLocal and RegAllocSimple directly call
>> storeRegToStackSlot, I would not found any calls to that method in
>> RegAllocLinearScan. Am I mi...