Richard Biener writes:
> On Tue, Sep 24, 2019 at 1:57 PM Richard Sandiford
> wrote:
>>
>> Richard Biener writes:
>> > On Tue, Sep 24, 2019 at 1:11 PM Richard Sandiford
>> > wrote:
>> >>
>> >> Martin Liška writes:
>> >> > Hi.
>> >> >
>> >> > The patch introduces couple of new TREE_CODEs that wi
On Tue, Sep 24, 2019 at 1:57 PM Richard Sandiford
wrote:
>
> Richard Biener writes:
> > On Tue, Sep 24, 2019 at 1:11 PM Richard Sandiford
> > wrote:
> >>
> >> Martin Liška writes:
> >> > Hi.
> >> >
> >> > The patch introduces couple of new TREE_CODEs that will help us to have
> >> > a proper GI
Richard Biener writes:
> On Tue, Sep 24, 2019 at 1:11 PM Richard Sandiford
> wrote:
>>
>> Martin Liška writes:
>> > Hi.
>> >
>> > The patch introduces couple of new TREE_CODEs that will help us to have
>> > a proper GIMPLE representation of current VECT_COND_EXPR. Right now,
>> > the first argum
On Tue, Sep 24, 2019 at 1:11 PM Richard Sandiford
wrote:
>
> Martin Liška writes:
> > Hi.
> >
> > The patch introduces couple of new TREE_CODEs that will help us to have
> > a proper GIMPLE representation of current VECT_COND_EXPR. Right now,
> > the first argument is typically a GENERIC tcc_expr
Martin Liška writes:
> Hi.
>
> The patch introduces couple of new TREE_CODEs that will help us to have
> a proper GIMPLE representation of current VECT_COND_EXPR. Right now,
> the first argument is typically a GENERIC tcc_expression tree with 2 operands
> that are visited at various places in GIMP
Hi.
The patch introduces couple of new TREE_CODEs that will help us to have
a proper GIMPLE representation of current VECT_COND_EXPR. Right now,
the first argument is typically a GENERIC tcc_expression tree with 2 operands
that are visited at various places in GIMPLE code. That said, based on the
