Displaying 3 results from an estimated 3 matches for "pqbp".
Did you mean:
pbqp
2011 Jan 08
0
[LLVMdev] Unreachable executed with fast Regalloc and Sparc backend
...3, D14, D15] in {
def CALL : InstSP<(outs), (ins calltarget:$dst),
"call $dst", []> {
bits<30> disp;
let op = 1;
let Inst{29-0} = disp;
}
The Uses=[O0,O1,O2,O3,O4,O5] is causing this crash (and similar crashes in the PQBP and Greedy allocators if I remember right). I fixed this in the MicroBlaze backend by remodeling the call instructions to be variadic like other backends. See the MBlazeInstrInfo.td changes in this commit:
http://www.llvm.org/viewvc/llvm-project?view=rev&revision=121994
NOTE: In the commit R1...
2011 Jan 07
2
[LLVMdev] Unreachable executed with fast Regalloc and Sparc backend
Hello,
When I run LLC with option "-O0 -march=sparc" on following testcase,
fast register allocator crashes with "UNREACHABLE executed" error. LLC
generates code successfully with other standard register allocators
available.
$ cat call.ll
define void @test() nounwind {
entry:
%0 = tail call i32 (...)* @foo() nounwind
tail call void (...)* @bar() nounwind
ret void
}
2008 Sep 20
0
[LLVMdev] Using VirtRegMap
...se keep in mind that some other allocators being currently developed use VirtRegMap with all its pros and cons. These allocators include an iterated coalescing graph colorging register allocator (Lang), a chordal graph register allocator (Fernando), a puzzle solving register allocator (Fernando), a PQBP register allocaor (Lang) and an extended linear scan register allocator (Roman). May be there are some other allocators as well.
And BTW, some other parts of the LLVM API related to register allocation are also used by other register allocators. So, any major changes to them may break them as wel...