[PATCH] D12246: [NVPTX] change threading intrinsics from noduplicate to convergent

[Owen Anderson via llvm-commits]

> On Aug 31, 2015, at 10:01 AM, Bjarke Roune <broune at google.com> wrote:
> 
> I'm not sure if you're saying that there should be no limitations as the use cases you had mind for convergent are always OK with such duplication, or that we should be figuring this stuff out on a case-by-case basis, or something else?

I designed the semantics of convergent to meet the needs of texture and gradient operations, without a lot of consideration for barriers.  IMO, It would be a nice end result if it turns out be just what barriers need as well, but I don’t want to accidentally hose the use cases I intended it for in pursuit of making it work for barriers.

Everything you’ve identified re: full vs partial unrolling, unstitching, etc. seems fine to me so far.

—Owen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20150831/c960c73f/attachment.html>