Displaying 4 results from an estimated 4 matches for "canevictinterference".
2012 Dec 18
2
[LLVMdev] LLVM ERROR: ran out of registers during register allocation
Hello Jakob,
> Those are some severe constraints on register allocation, but it ought to
> be possible anyway.
>
Indeed, these constraints aren't playing very well with the register
allocator :\
>
> You may wan't to investigate how RAGreedy::canEvictInterference() is
> behaving.
>
Ok, this is what I've noticed, not sure if it makes sense at all but,
regalloc fails with the following sequence:
1) directly assign the physreg in PTR RC to a virtX.
2) for a virtY which also belongs to the PTR RC, try to evict: call
canEvictInterference() for virtY...
2012 Dec 17
0
[LLVMdev] LLVM ERROR: ran out of registers during register allocation
...a solution or a workaround will be greatly appreciated since this problem is severily limiting the complexity of the programs that I can currently compile.
Those are some severe constraints on register allocation, but it ought to be possible anyway.
You may wan't to investigate how RAGreedy::canEvictInterference() is behaving.
/jakob
2012 Dec 17
2
[LLVMdev] LLVM ERROR: ran out of registers during register allocation
Hello,
I'm getting the "LLVM ERROR: ran out of registers during register
allocation" error message for an out of tree target I'm developing. This is
happening for the following piece of C code:
struct ss
{
int a;
int b;
int c;
};
void loop(struct ss *x, struct ss **y, int z)
{
int i;
for (i=0; i<z; ++i)
{
x->c += y[i]->b;
}
}
The problem relies in
2012 Dec 19
0
[LLVMdev] LLVM ERROR: ran out of registers during register allocation
...t;
>> Those are some severe constraints on register allocation, but it ought to
>> be possible anyway.
>>
>
> Indeed, these constraints aren't playing very well with the register
> allocator :\
>
>
>>
>> You may wan't to investigate how RAGreedy::canEvictInterference() is
>> behaving.
>>
>
> Ok, this is what I've noticed, not sure if it makes sense at all but,
> regalloc fails with the following sequence:
>
> 1) directly assign the physreg in PTR RC to a virtX.
> 2) for a virtY which also belongs to the PTR RC, try to evict: ca...