Displaying 3 results from an estimated 3 matches for "splitanalysis".
2011 Jan 20
0
[LLVMdev] [LLVMDev] Live Intervals and Finding the next usage
..., 2011, at 5:37 AM, Jeff Kunkel wrote:
> I have a live interval, and I would like to find out what SlotIndex the next use the register will occur? Is there any way to map a live interval back into instructions or SlotIndexes or blocks used by?
Not really, you have to use the use-def chain. See SplitAnalysis::analyzeUses().
/jakob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1929 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110120/c34b5fca/attachment.bin>
2011 Jan 20
4
[LLVMdev] [LLVMDev] Live Intervals and Finding the next usage
I have a live interval, and I would like to find out what SlotIndex the next
use the register will occur? Is there any way to map a live interval back
into instructions or SlotIndexes or blocks used by?
- Thanks
Jeff Kunkel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110120/fd429dbd/attachment.html>
2011 May 02
2
[LLVMdev] LiveVariables not updated in MachineBasicBlock::SplitCriticalEdge?
...is fired when I run llc
with -march=mipsel -mcpu=4ke. It seems to me that the root cause of this
assertion is the piece of code shown above that is called during PHI nodes
elimination (llc exits normally if I add -disable-phi-elim-edge-splitting).
llc: llvm/lib/CodeGen/SplitKit.cpp:170: bool
llvm::SplitAnalysis::calcLiveBlockInfo(): Assertion `BI.FirstUse >= Start'
failed.
The following is the Machine IR and LiveVariables::ValInfo dump before and
after PHI nodes elimination.
1. Before PHI nodes elimination.
-Machine IR:
BB#14: derived from LLVM BB %for.cond151.preheader
Predecessors accordin...