RFC: Enable vectorization of call instructions in the loop vectorizer

Renato Golin renato.golin at linaro.org
Mon Dec 16 13:48:30 PST 2013

On 16 December 2013 21:08, Arnold Schwaighofer <aschwaighofer at apple.com>wrote:

> Yes and we can easily model this in the cost model by asking what is the
> cost of a (library) function call (vectorized or not) and have this return
> a reasonably high value.

I'm wondering, in the case Nadav said about #pragma vectorize, how are we
going to tell the compiler what is the cost of this or that vector-variant
of foo?

When the cost tables can change independently of user-code, this looks like
a tom&jerry exercise.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20131216/27eb289d/attachment.html>

More information about the llvm-commits mailing list