On Tue, Apr 8, 2014 at 2:52 AM, Eric Anholt wrote:
> Chia-I Wu writes:
>
>> From: Chia-I Wu
>>
>> Given
>>
>> mov vgrf7, vgrf9.xyxz
>> add vgrf9.xyz, vgrf4.xyzw, vgrf5.xyzw
>> add vgrf10.x, vgrf6.xyzw, vgrf7.
>>
>> the last instruction would be wrongly changed to
>>
>> add vgrf10.x,
Chia-I Wu writes:
> From: Chia-I Wu
>
> Given
>
> mov vgrf7, vgrf9.xyxz
> add vgrf9.xyz, vgrf4.xyzw, vgrf5.xyzw
> add vgrf10.x, vgrf6.xyzw, vgrf7.
>
> the last instruction would be wrongly changed to
>
> add vgrf10.x, vgrf6.xyzw, vgrf9.
>
> during copy propagation.
>
> The issue
On 04/06/2014 09:31 PM, Chia-I Wu wrote:
> From: Chia-I Wu
>
> Given
>
> mov vgrf7, vgrf9.xyxz
> add vgrf9.xyz, vgrf4.xyzw, vgrf5.xyzw
> add vgrf10.x, vgrf6.xyzw, vgrf7.
>
> the last instruction would be wrongly changed to
>
> add vgrf10.x, vgrf6.xyzw, vgrf9.
>
> during copy p
From: Chia-I Wu
Given
mov vgrf7, vgrf9.xyxz
add vgrf9.xyz, vgrf4.xyzw, vgrf5.xyzw
add vgrf10.x, vgrf6.xyzw, vgrf7.
the last instruction would be wrongly changed to
add vgrf10.x, vgrf6.xyzw, vgrf9.
during copy propagation.
The issue is that when deciding if a record should be