Francisco Jerez writes:
> Iago Toral writes:
>
>> On Fri, 2015-07-31 at 13:12 +0300, Francisco Jerez wrote:
>>> Iago Toral writes:
>>>
>>> > On Thu, 2015-07-30 at 17:08 +0300, Francisco Jerez wrote:
>>> >> Iago Toral Quiroga writes:
>>> >>
>>> >> > When we have code such as this:
>>> >> >
>>
Iago Toral writes:
> On Thu, 2015-07-30 at 17:08 +0300, Francisco Jerez wrote:
>> Iago Toral Quiroga writes:
>>
>> > When we have code such as this:
>> >
>> > mov vgrf1.0.x:F, vgrf2.:F
>> > mov vgrf3.0.x:F, vgrf1.:F
>> > ...
>> > mov vgrf3.0.x:F, vgrf1.:F
>> >
>> > And vgrf1 is chos
Iago Toral writes:
> On Fri, 2015-07-31 at 13:12 +0300, Francisco Jerez wrote:
>> Iago Toral writes:
>>
>> > On Thu, 2015-07-30 at 17:08 +0300, Francisco Jerez wrote:
>> >> Iago Toral Quiroga writes:
>> >>
>> >> > When we have code such as this:
>> >> >
>> >> > mov vgrf1.0.x:F, vgrf2.:F
>
On Thu, 2015-07-30 at 17:08 +0300, Francisco Jerez wrote:
> Iago Toral Quiroga writes:
>
> > When we have code such as this:
> >
> > mov vgrf1.0.x:F, vgrf2.:F
> > mov vgrf3.0.x:F, vgrf1.:F
> > ...
> > mov vgrf3.0.x:F, vgrf1.:F
> >
> > And vgrf1 is chosen for spilling, we can emit this
On Fri, 2015-07-31 at 13:12 +0300, Francisco Jerez wrote:
> Iago Toral writes:
>
> > On Thu, 2015-07-30 at 17:08 +0300, Francisco Jerez wrote:
> >> Iago Toral Quiroga writes:
> >>
> >> > When we have code such as this:
> >> >
> >> > mov vgrf1.0.x:F, vgrf2.:F
> >> > mov vgrf3.0.x:F, vgrf1.xx
On Fri, 2015-07-31 at 13:12 +0300, Francisco Jerez wrote:
> Iago Toral writes:
>
> > On Thu, 2015-07-30 at 17:08 +0300, Francisco Jerez wrote:
> >> Iago Toral Quiroga writes:
> >>
> >> > When we have code such as this:
> >> >
> >> > mov vgrf1.0.x:F, vgrf2.:F
> >> > mov vgrf3.0.x:F, vgrf1.xx
Francisco Jerez writes:
> Iago Toral writes:
>
>> On Thu, 2015-07-30 at 17:08 +0300, Francisco Jerez wrote:
>>> Iago Toral Quiroga writes:
>>>
>>> > When we have code such as this:
>>> >
>>> > mov vgrf1.0.x:F, vgrf2.:F
>>> > mov vgrf3.0.x:F, vgrf1.:F
>>> > ...
>>> > mov vgrf3.0.x:F, vg
Iago Toral writes:
> On Thu, 2015-07-30 at 17:14 +0300, Francisco Jerez wrote:
>> Francisco Jerez writes:
>>
>> > Iago Toral Quiroga writes:
>> >
>> >> When we have code such as this:
>> >>
>> >> mov vgrf1.0.x:F, vgrf2.:F
>> >> mov vgrf3.0.x:F, vgrf1.:F
>> >> ...
>> >> mov vgrf3.0.x:F,
Iago Toral writes:
> On Thu, 2015-07-30 at 17:08 +0300, Francisco Jerez wrote:
>> Iago Toral Quiroga writes:
>>
>> > When we have code such as this:
>> >
>> > mov vgrf1.0.x:F, vgrf2.:F
>> > mov vgrf3.0.x:F, vgrf1.:F
>> > ...
>> > mov vgrf3.0.x:F, vgrf1.:F
>> >
>> > And vgrf1 is chos
On Thu, 2015-07-30 at 17:08 +0300, Francisco Jerez wrote:
> Iago Toral Quiroga writes:
>
> > When we have code such as this:
> >
> > mov vgrf1.0.x:F, vgrf2.:F
> > mov vgrf3.0.x:F, vgrf1.:F
> > ...
> > mov vgrf3.0.x:F, vgrf1.:F
> >
> > And vgrf1 is chosen for spilling, we can emit this
On Thu, 2015-07-30 at 17:14 +0300, Francisco Jerez wrote:
> Francisco Jerez writes:
>
> > Iago Toral Quiroga writes:
> >
> >> When we have code such as this:
> >>
> >> mov vgrf1.0.x:F, vgrf2.:F
> >> mov vgrf3.0.x:F, vgrf1.:F
> >> ...
> >> mov vgrf3.0.x:F, vgrf1.:F
> >>
> >> And vgrf1
Francisco Jerez writes:
> Iago Toral Quiroga writes:
>
>> When we have code such as this:
>>
>> mov vgrf1.0.x:F, vgrf2.:F
>> mov vgrf3.0.x:F, vgrf1.:F
>> ...
>> mov vgrf3.0.x:F, vgrf1.:F
>>
>> And vgrf1 is chosen for spilling, we can emit this:
>>
>> mov vgrf1.0.x:F, vgrf2.:F
>>
Iago Toral Quiroga writes:
> When we have code such as this:
>
> mov vgrf1.0.x:F, vgrf2.:F
> mov vgrf3.0.x:F, vgrf1.:F
> ...
> mov vgrf3.0.x:F, vgrf1.:F
>
> And vgrf1 is chosen for spilling, we can emit this:
>
> mov vgrf1.0.x:F, vgrf2.:F
> gen4_scratch_write hw_reg0:F, vgrf1.
When we have code such as this:
mov vgrf1.0.x:F, vgrf2.:F
mov vgrf3.0.x:F, vgrf1.:F
...
mov vgrf3.0.x:F, vgrf1.:F
And vgrf1 is chosen for spilling, we can emit this:
mov vgrf1.0.x:F, vgrf2.:F
gen4_scratch_write hw_reg0:F, vgrf1.:D, 22D
mov vgrf3.0.x:F, vgrf1.:F
...
gen4_s
14 matches
Mail list logo