search for: my_pointer

...e same function context. The mem accesses in the parallel loop iteration could have a metadata "llvm.mem.parallel_loop_iter 0 0" or similar where the first id is a loop id, the latter the iteration id. Restricted pointer mem accesses could use metadata "llvm.mem.restrict my_function my_pointer". A parallel loop alias analyzer can use the parallel_loop_iter metadata (if loop id equals but iteration id doesn't, return NO_ALIAS) and a restrict pointer AA use the latter (if both of the queried pointers have it and it differs for the pointer part only, return NO_ALIAS). -- --Pekka

On 01/28/2013 12:58 PM, Pekka Jääskeläinen wrote: > Hi, > > Attached is a patch which uses a simple "parallel_loop" metadata attached > to the loop branch instruction in the loop latch for skipping > cross-iteration > memory dependency checking in the LoopVectorizer. This was briefly > discussed > in the email thread "LoopVectorizer in OpenCL C work group

Hi, Attached is a patch which uses a simple "parallel_loop" metadata attached to the loop branch instruction in the loop latch for skipping cross-iteration memory dependency checking in the LoopVectorizer. This was briefly discussed in the email thread "LoopVectorizer in OpenCL C work group autovectorization". It also converts the "min iteration count to vectorize"