On Sun, Jan 31, 2016 at 7:29 PM, Dave Airlie wrote:
> On 30 January 2016 at 07:00, Ilia Mirkin wrote:
>> We use this logic to detect live ranges and then do plain renaming
>> across the whole codebase. As such, to prevent WaW hazards, we have to
>> treat a write as if it were also a read.
>>
>> F
On 30 January 2016 at 07:00, Ilia Mirkin wrote:
> We use this logic to detect live ranges and then do plain renaming
> across the whole codebase. As such, to prevent WaW hazards, we have to
> treat a write as if it were also a read.
>
> For example, the following sequence was observed before this
We use this logic to detect live ranges and then do plain renaming
across the whole codebase. As such, to prevent WaW hazards, we have to
treat a write as if it were also a read.
For example, the following sequence was observed before this patch:
13: UIF TEMP[6]. :0
14: ADD TEMP[6].x, CON
