Displaying 3 results from an estimated 3 matches for "uncoallesce".
Did you mean:
coallesce
2006 Dec 23
1
[LLVMdev] Possible bug in the linear scan register allocator
...11:
>This is due to the coallescer coallescing virtregs with both EAX and
>EDX, which makes them unavailable to satisfy spills, causing the RA to
>run out of registers. We want to coallesce physregs when possible,
>but we cannot pin them in the spiller:
>we have to be able to >uncoallesce them.
First of all, I totally agree with "we have to be able to uncoallesce
them". Linear Scan already does a backtracking in some situations. I'm
wondering, if it is very difficult to implement the logic, where when
it detects that it runs for ever (i.e. nothing can be spilled for...
2006 Dec 22
0
[LLVMdev] Possible bug in the linear scan register allocator
On Thu, 21 Dec 2006, Roman Levenstein wrote:
> following:
> 1) some of the fixed registers intervals are merged with some virtual
> registers intervals
> 2) later there is a need to spill one of the allocated registers, but
> since all joined intervals are FIXED intervals now due to (1), they
> cannot be spilled. Therefore, the register allocator loops for ever.
>
> I would
2006 Dec 21
1
[LLVMdev] Possible bug in the linear scan register allocator
Hi,
I was working on extending soft-float support for handling expansion of
i64 and f64 into i16, i.e. on supporting the expansion of long values
of illegal types into more then two parts. For that I modified
SelectionDAGLowering::getValue() and several other functions.
This seems to work now on my test-cases, but while testing it I ran
into a different problem. I have the impression that I