Displaying 2 results from an estimated 2 matches for "vreg368".
Did you mean:
vreg36
2014 Sep 05
3
[LLVMdev] [PATCH] [MachineSinking] Conservatively clear kill flags after coalescing.
...own out-of-tree target, and we have not been able to reproduce this problem on an in-tree target. /Patrik Hägglund
[MachineSinking] Conservatively clear kill flags after coalescing.
This solves the problem of having a kill flag inside a loop
with a definition of the register prior to the loop:
%vreg368<def> ...
Inside loop:
%vreg520<def> = COPY %vreg368
%vreg568<def,tied1> = add %vreg341<tied0>, %vreg520<kill>
=> was coalesced into =>
%vreg568<def,tied1> = add %vreg341<tied0>, %vreg368<kill>
MachineVerifier then co...
2014 Sep 05
5
[LLVMdev] [PATCH] [MachineSinking] Conservatively clear kill flags after coalescing.
...target. /PatrikHägglund
>>>
>>> [MachineSinking] Conservatively clear kill flags after coalescing.
>>>
>>> This solves the problem of having a kill flag inside a loop
>>> with a definition of the register prior to the loop:
>>>
>>> %vreg368<def> ...
>>>
>>> Inside loop:
>>>
>>> %vreg520<def> = COPY %vreg368
>>> %vreg568<def,tied1> = add %vreg341<tied0>, %vreg520<kill>
>>>
>>> => was coalesced into =>
>>>
>&g...