Iago Toral writes:
> On Tue, 2016-05-10 at 16:53 -0700, Francisco Jerez wrote:
>> Samuel Iglesias Gonsálvez writes:
>>
>> > From: Iago Toral Quiroga
>> >
>> > We were not accounting for reg_suboffset in the check for the start
>> > of the region. This meant that would allow copy-propagation ev
Iago Toral writes:
> On Tue, 2016-05-10 at 16:53 -0700, Francisco Jerez wrote:
>> Samuel Iglesias Gonsálvez writes:
>>
>> > From: Iago Toral Quiroga
>> >
>> > We were not accounting for reg_suboffset in the check for the start
>> > of the region. This meant that would allow copy-propagation ev
On Tue, 2016-05-10 at 16:53 -0700, Francisco Jerez wrote:
> Samuel Iglesias Gonsálvez writes:
>
> > From: Iago Toral Quiroga
> >
> > We were not accounting for reg_suboffset in the check for the start
> > of the region. This meant that would allow copy-propagation even if
> > the dst wrote to su
Francisco Jerez writes:
> Samuel Iglesias Gonsálvez writes:
>
>> From: Iago Toral Quiroga
>>
>> We were not accounting for reg_suboffset in the check for the start
>> of the region. This meant that would allow copy-propagation even if
>> the dst wrote to sub_regoffset 4 and our source read from
Samuel Iglesias Gonsálvez writes:
> From: Iago Toral Quiroga
>
> We were not accounting for reg_suboffset in the check for the start
> of the region. This meant that would allow copy-propagation even if
> the dst wrote to sub_regoffset 4 and our source read from
> sub_regoffset 0, which is not c
On Tue, 2016-05-03 at 17:28 -0700, Jordan Justen wrote:
> On 2016-05-03 05:21:55, Samuel Iglesias Gonsálvez wrote:
> > From: Iago Toral Quiroga
> >
> > We were not accounting for reg_suboffset in the check for the start
> > of the region. This meant that would allow copy-propagation even if
> > t
On Tue, 2016-05-03 at 17:37 -0700, Jason Ekstrand wrote:
>
>
> On Tue, May 3, 2016 at 5:21 AM, Samuel Iglesias Gonsálvez
> wrote:
> From: Iago Toral Quiroga
>
> We were not accounting for reg_suboffset in the check for the
> start
> of the region. This m
On Tue, May 3, 2016 at 5:21 AM, Samuel Iglesias Gonsálvez <
sigles...@igalia.com> wrote:
> From: Iago Toral Quiroga
>
> We were not accounting for reg_suboffset in the check for the start
> of the region. This meant that would allow copy-propagation even if
> the dst wrote to sub_regoffset 4 and
On 2016-05-03 05:21:55, Samuel Iglesias Gonsálvez wrote:
> From: Iago Toral Quiroga
>
> We were not accounting for reg_suboffset in the check for the start
> of the region. This meant that would allow copy-propagation even if
> the dst wrote to sub_regoffset 4 and our source read from
> sub_regof
From: Iago Toral Quiroga
We were not accounting for reg_suboffset in the check for the start
of the region. This meant that would allow copy-propagation even if
the dst wrote to sub_regoffset 4 and our source read from
sub_regoffset 0, which is not correct. This was observed in fp64 code,
since t
10 matches
Mail list logo