On June 22, 2017 6:20:57 PM GMT+02:00, Alan Hayward
wrote:
>
>> On 22 Jun 2017, at 12:54, Richard Biener wrote:
>>
>> On Thu, 22 Jun 2017, Alan Hayward wrote:
>>
>>>
On 22 Jun 2017, at 09:52, Richard Biener wrote:
On Thu, 22 Jun 2017, Richard Biener wrote:
> On Wed,
> On 22 Jun 2017, at 12:54, Richard Biener wrote:
>
> On Thu, 22 Jun 2017, Alan Hayward wrote:
>
>>
>>> On 22 Jun 2017, at 09:52, Richard Biener wrote:
>>>
>>> On Thu, 22 Jun 2017, Richard Biener wrote:
>>>
On Wed, 21 Jun 2017, Richard Biener wrote:
>
> During my attempt
On Thu, 22 Jun 2017, Alan Hayward wrote:
>
> > On 22 Jun 2017, at 09:52, Richard Biener wrote:
> >
> > On Thu, 22 Jun 2017, Richard Biener wrote:
> >
> >> On Wed, 21 Jun 2017, Richard Biener wrote:
> >>
> >>>
> >>> During my attempt to refactor reduction vectorization I ran across
> >>> the
> On 22 Jun 2017, at 09:52, Richard Biener wrote:
>
> On Thu, 22 Jun 2017, Richard Biener wrote:
>
>> On Wed, 21 Jun 2017, Richard Biener wrote:
>>
>>>
>>> During my attempt to refactor reduction vectorization I ran across
>>> the special casing of inital values for INTEGER_INDUC_COND_REDUCTI
On Thu, 22 Jun 2017, Richard Biener wrote:
> On Wed, 21 Jun 2017, Richard Biener wrote:
>
> >
> > During my attempt to refactor reduction vectorization I ran across
> > the special casing of inital values for INTEGER_INDUC_COND_REDUCTION
> > and tried to see what it is about. So I ended up impl
On Wed, 21 Jun 2017, Richard Biener wrote:
>
> During my attempt to refactor reduction vectorization I ran across
> the special casing of inital values for INTEGER_INDUC_COND_REDUCTION
> and tried to see what it is about. So I ended up implementing
> cond reduction support for targets w/o REDUC_
During my attempt to refactor reduction vectorization I ran across
the special casing of inital values for INTEGER_INDUC_COND_REDUCTION
and tried to see what it is about. So I ended up implementing
cond reduction support for targets w/o REDUC_MAX_EXPR by simply
doing the reduction in scalar code
