On Fri, Sep 2, 2011 at 11:43 AM, Richard Guenther wrote:
>> > > >> >> > Hmm. But then I'd have to try emit an insn, right? Currently
>> > > >> >> > the vectorizer simply looks for an optab handler ... the
>> > > >> >> > operands are not readily available (but their mode is known).
>> > > >> >>
On Tue, 30 Aug 2011, Richard Guenther wrote:
> On Tue, 30 Aug 2011, Richard Guenther wrote:
>
> > On Tue, 30 Aug 2011, Uros Bizjak wrote:
> >
> > > On Tue, Aug 30, 2011 at 11:15 AM, Richard Guenther
> > > wrote:
> > >
> > > >> >> > Hmm. But then I'd have to try emit an insn, right? Currentl
On Tue, 30 Aug 2011, Richard Guenther wrote:
> On Tue, 30 Aug 2011, Uros Bizjak wrote:
>
> > On Tue, Aug 30, 2011 at 11:15 AM, Richard Guenther
> > wrote:
> >
> > >> >> > Hmm. But then I'd have to try emit an insn, right? Currently
> > >> >> > the vectorizer simply looks for an optab handler
On Tue, 30 Aug 2011, Uros Bizjak wrote:
> On Tue, Aug 30, 2011 at 11:15 AM, Richard Guenther wrote:
>
> >> >> > Hmm. But then I'd have to try emit an insn, right? Currently
> >> >> > the vectorizer simply looks for an optab handler ... the
> >> >> > operands are not readily available (but thei
On Tue, Aug 30, 2011 at 11:15 AM, Richard Guenther wrote:
>> >> > Hmm. But then I'd have to try emit an insn, right? Currently
>> >> > the vectorizer simply looks for an optab handler ... the
>> >> > operands are not readily available (but their mode is known).
>> >> > So I'd create some fake r
On Tue, 30 Aug 2011, Uros Bizjak wrote:
> On Tue, Aug 30, 2011 at 11:07 AM, Jakub Jelinek wrote:
> > On Tue, Aug 30, 2011 at 11:02:02AM +0200, Uros Bizjak wrote:
> >> > Hmm. But then I'd have to try emit an insn, right? Currently
> >> > the vectorizer simply looks for an optab handler ... the
>
On Tue, Aug 30, 2011 at 11:07 AM, Jakub Jelinek wrote:
> On Tue, Aug 30, 2011 at 11:02:02AM +0200, Uros Bizjak wrote:
>> > Hmm. But then I'd have to try emit an insn, right? Currently
>> > the vectorizer simply looks for an optab handler ... the
>> > operands are not readily available (but their
On Tue, 30 Aug 2011, Jakub Jelinek wrote:
> On Tue, Aug 30, 2011 at 11:02:02AM +0200, Uros Bizjak wrote:
> > > Hmm. But then I'd have to try emit an insn, right? Currently
> > > the vectorizer simply looks for an optab handler ... the
> > > operands are not readily available (but their mode is k
On Tue, Aug 30, 2011 at 11:02:02AM +0200, Uros Bizjak wrote:
> > Hmm. But then I'd have to try emit an insn, right? Currently
> > the vectorizer simply looks for an optab handler ... the
> > operands are not readily available (but their mode is known).
> > So I'd create some fake regs, setup oper
On Tue, Aug 30, 2011 at 10:50 AM, Richard Guenther wrote:
>> > Hm, ok - that was the first variant I tried (well, but with modeless
>> > operands 1 and 2, to keep 4 and 5 selcting int vs. fp compare). But
>> > modeless operands get you that annoying warning from the gen* programs.
>>
>> Only fo
On Tue, 30 Aug 2011, Uros Bizjak wrote:
> On Mon, Aug 29, 2011 at 9:44 PM, Richard Guenther wrote:
>
> >> > This patch makes a conversion optab from the direct optabs vcond
> >> > and vcondu. This allows to specify different modes for the
> >> > actual comparison and the value that is selected.
On Mon, Aug 29, 2011 at 9:44 PM, Richard Guenther wrote:
>> > This patch makes a conversion optab from the direct optabs vcond
>> > and vcondu. This allows to specify different modes for the
>> > actual comparison and the value that is selected.
>> >
>> > All targets but i386 are trivially conve
On Mon, 29 Aug 2011, Uros Bizjak wrote:
> On Mon, Aug 29, 2011 at 4:31 PM, Richard Guenther wrote:
>
> > This patch makes a conversion optab from the direct optabs vcond
> > and vcondu. This allows to specify different modes for the
> > actual comparison and the value that is selected.
> >
> >
On Mon, Aug 29, 2011 at 4:31 PM, Richard Guenther wrote:
> This patch makes a conversion optab from the direct optabs vcond
> and vcondu. This allows to specify different modes for the
> actual comparison and the value that is selected.
>
> All targets but i386 are trivially converted by
> s/vco
On Mon, 29 Aug 2011, Richard Guenther wrote:
>
> This patch makes a conversion optab from the direct optabs vcond
> and vcondu. This allows to specify different modes for the
> actual comparison and the value that is selected.
>
> All targets but i386 are trivially converted by
> s/vcond/vcond
This patch makes a conversion optab from the direct optabs vcond
and vcondu. This allows to specify different modes for the
actual comparison and the value that is selected.
All targets but i386 are trivially converted by
s/vcond/vcond/. The i386 port is enhanced
to support a OP b ? c : d as (
16 matches
Mail list logo