RFC: Enable vectorization of call instructions in the loop vectorizer
listmail at philipreames.com
Tue Dec 17 11:10:44 PST 2013
On 12/16/13 9:08 AM, James Molloy wrote:
> So the version attached reads metadata attached to CallInsts. The
> schema for the metadata is detailed in the proposed LangRef addition,
> but basically it describes a list of potential vectorization
> candidates. Each candidate has a vector width, a llvm::Function* (or
> MDString) giving the target function and a string describing how the
> function arguments need to be handled.
Specifically with regards to metadata, why is the metadata on the call
site not the function declaration? I would expect that a call to "cos"
would always vectorize to the same "cos4". Is supporting different
vectorizations at different points of the program a key goal?
Ignoring most of the discussion since it seems like a good conclusion
has been reached.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-commits