Displaying 2 results from an estimated 2 matches for "vreg1956".
Did you mean:
vreg1954
2014 Aug 22
2
[LLVMdev] Help with definition of subregisters; spill, rematerialization and implicit uses
...954:0 at 5000r may remat from %vreg1954:hi16<def,read-undef>
= mv_any16 32766
And it examines all use points of vreg1954 to see if it can remat or not:
cannot remat for 5128e %vreg223<def> = COPY %vreg1954
cannot remat for 5216e %vreg1178<def> = COPY %vreg1954
remat: 5044r %vreg1956:hi16<def,read-undef> = mv_any16 32766
5048e mv_ar16_r16_rmod1 %vreg1956:hi16<kill>, %vreg1753
cannot remat for 5064e Store40FI %vreg1954, <fi#2>
cannot remat for 5348e %vreg1955<def> = COPY %vreg1954
All defs dead: %vreg1954:hi16<def,read-undef,dead> = mv...
2014 Aug 19
2
[LLVMdev] Help with definition of subregisters; spill, rematerialization and implicit uses
Hi Quentin,
On 08/15/14 19:01, Quentin Colombet wrote:
[...]
>> The question is: How should true subregister definitions be
>> expressed so that they do not interfere with each other? See the
>> detailed problem description below.
>
> We do have a limitation in our current liveness tracking for
> sub-register. Therefore, I am not sure that is possible.
>
>