search for: getnextvalu

Displaying 4 results from an estimated 4 matches for "getnextvalu".

Did you mean: getnextvalue
2007 Oct 06
2
[LLVMdev] Spill Interval Generation Question
...'s always the case that the source live interval's value "end" is the def slot for the instruction. In LiveIntervalAnalysis::addIntervalsForSpills, we have this: if (HasUse) { LiveRange LR(getLoadIndex(index), getUseIndex(index), nI.getNextValue(~0U, 0, VNInfoAllocator)); DOUT << " +" << LR; nI.addRange(LR); } Should this actually extend from the load index to the def index since value intervals are exclusive at end? Otherwise, the interval for the spill doesn't include the us...
2007 Oct 08
0
[LLVMdev] Spill Interval Generation Question
On Oct 5, 2007, at 5:52 PM, David Greene wrote: > > In LiveIntervalAnalysis::addIntervalsForSpills, we have this: > > if (HasUse) { > LiveRange LR(getLoadIndex(index), getUseIndex(index), > nI.getNextValue(~0U, 0, VNInfoAllocator)); > DOUT << " +" << LR; > nI.addRange(LR); > } > > Should this actually extend from the load index to the def index since > value intervals are exclusive at end? Otherwise, the interval for > t...
2014 Oct 14
2
[LLVMdev] Problem of stack slot coloring
...spillAll() { > // Update LiveStacks now that we are committed to spilling. > if (StackSlot == VirtRegMap::NO_STACK_SLOT) { > StackSlot = VRM.assignVirt2StackSlot(Original); > StackInt = &LSS.getOrCreateInterval(StackSlot, MRI.getRegClass(Original)); > StackInt->getNextValue(SlotIndex(), LSS.getVNInfoAllocator()); > } else > StackInt = &LSS.getInterval(StackSlot); > > if (Original != Edit->getReg()) > VRM.assignVirt2StackSlot(Edit->getReg(), StackSlot); > > assert(StackInt->getNumValNums() == 1 && "Bad stack...
2014 Oct 13
2
[LLVMdev] Problem of stack slot coloring
Hi, Can anyone help me with the stack slot coloring optimization? This corresponding file is /lib/codegen/stackslotcoloring.cpp. It is said this optimization was for stack slot overlay for frame size reduction, after register allocation phase. And this transformation pass relies on the LiveStack analysis pass. How, when checking the source code, it seems the LiveStack analysis has not been