[PATCH] support llvm.vectorization.vector_width metadata

[Arnold Schwaighofer]

That would be great. I think the following annotations would be useful:

llvm.vectorization.unroll
llvm.vectorization.force (vectorize without consulting the cost model)
llvm.vectorization.disable (don’t vectorize)

Thanks

On May 24, 2013, at 1:25 PM, "Redmond, Paul" <paul.redmond at intel.com> wrote:

> Sure. Should I also add support for llvm.vectorization.unroll? Are there any other obvious hints?
> 
> On 2013-05-24, at 2:22 PM, Arnold Schwaighofer wrote:
> 
>> 
>> On May 24, 2013, at 12:49 PM, "Redmond, Paul" <paul.redmond at intel.com> wrote:
>> 
>>> Hi,
>>> 
>>> The attached patch modifies LoopVectorizer to recognize llvm.vectorization.vector_width metadata attached to llvm.loop metadata.
>>> 
>>> The llvm.loop.parallel metadata has been renamed to llvm.loop to be more generic. Loop::isAnnotatedParallel now looks for llvm.loop and associated llvm.mem.parallel_loop_access. If we decide that we still need an explicit llvm.loop.parallel metadata then it can be added as a child of llvm.loop.
>>> 
>> 
>> Can you also include an update to the LangRef.
>> 
>> 
>> Thanks
>> 
>> 
>>> Loop::setLoopID was added for symmetry and it is used in a forthcoming patch which preserves llvm.loop metadata in loop passes.
>>> 
>>> paul
>>> 
>>> <Mail Attachment>_______________________________________________
>>> llvm-commits mailing list
>>> llvm-commits at cs.uiuc.edu
>>> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits