search for: unrollcnt

...two kind of metadata: llvm.loop.parallel (attached to each loop latch) and llvm.mem.parallel (attached to each memory instruction!). I think that the motivation for the first metadata is clear - it says that the loop is data-parallel. I can also see us adding additional metadata such as llvm.loop.unrollcnt to allow the users to control the unroll count of loops using pragmas. That's fine. Pekka, can you think of transformations that may need invalidate or take this metadata into consideration ? Regarding the second metadata that you proposed, I am a bit skeptical. I don't fully understand th...

...allel >> (attached to each loop latch) and llvm.mem.parallel (attached to each memory >> instruction!). I think that the motivation for the first metadata is clear - >> it says that the loop is data-parallel. I can also see us adding additional >> metadata such as llvm.loop.unrollcnt to allow the users to control the unroll >> count of loops using pragmas. That's fine. Pekka, can you think of >> transformations that may need invalidate or take this metadata into >> consideration ? > > Any pass that introduces new non-parallel memory instructions to...

...a: llvm.loop.parallel > (attached to each loop latch) and llvm.mem.parallel (attached to each memory > instruction!). I think that the motivation for the first metadata is clear - > it says that the loop is data-parallel. I can also see us adding additional > metadata such as llvm.loop.unrollcnt to allow the users to control the unroll > count of loops using pragmas. That's fine. Pekka, can you think of > transformations that may need invalidate or take this metadata into > consideration ? Any pass that introduces new non-parallel memory instructions to the loop, because they...

...(attached to each loop latch) and llvm.mem.parallel (attached to each memory > >> instruction!). I think that the motivation for the first metadata is clear - > >> it says that the loop is data-parallel. I can also see us adding additional > >> metadata such as llvm.loop.unrollcnt to allow the users to control the unroll > >> count of loops using pragmas. That's fine. Pekka, can you think of > >> transformations that may need invalidate or take this metadata into > >> consideration ? > > > > Any pass that introduces new non-paralle...

...to each loop latch) and llvm.mem.parallel (attached to each memory >>>> instruction!). I think that the motivation for the first metadata is clear - >>>> it says that the loop is data-parallel. I can also see us adding additional >>>> metadata such as llvm.loop.unrollcnt to allow the users to control the unroll >>>> count of loops using pragmas. That's fine. Pekka, can you think of >>>> transformations that may need invalidate or take this metadata into >>>> consideration ? >>> >>> Any pass that introduces n...

...t; (attached to each loop latch) and llvm.mem.parallel (attached to each memory >>> instruction!). I think that the motivation for the first metadata is clear - >>> it says that the loop is data-parallel. I can also see us adding additional >>> metadata such as llvm.loop.unrollcnt to allow the users to control the unroll >>> count of loops using pragmas. That's fine. Pekka, can you think of >>> transformations that may need invalidate or take this metadata into >>> consideration ? >> >> Any pass that introduces new non-parallel memo...