[RFC] optabs and tree-codes for vector operations

[Dorit Naishlos]

> > - "storefloor":
> >   optab: store_floor_optab
>
> Which is exactly what I was trying to avoid -- two separate sets of
optabs.

ok. addr_floor_optab?

> Yes, we could, but again, the whole point is to use one register for both
> address and "magic", rather than two registers.

ok.

> > Is there an added value for
> > exposing it to the vectorizer
> > ...
>
> It'll be much harder to reduce the register pressure by one after the
fact.

> > Can the builtin be encapsulated within REALIGN_LOAD_EXPR
> > ? i.e - have a REALIGN_LOAD_EXPR(v1,v2,addr) that on some targets will
be
> > expanded to {x=builtin(addr),smthing(v1,v2,x)} and on other targets
will be
> > expanded directly to {smthing(v1,v2,addr)}?
>
> No.  Gimple doesn't work that way.

Can you please explain the above two comments?


thanks,
dorit