On 11/21/2014 12:14 AM, Anastasia Stulova wrote:
Ok. If there are multiple use cases for this, perhaps, it's worth trying to
add 'private' to the list of OpenCL address spaces in Clang.

On 11/17/2014 10:41 AM, Anastasia Stulova wrote:
One of the difficulty is that Clang currently treats private address
space just the same as if no address space qualifier was specified.
That makes it difficult to find a right place to handle the default
address space behaviour, because information becomes unavailable early on.

The provisional SPIR 2.0 generator from Khronos seems to handle this already. Would you consider porting that code to trunk? As far as I know, the OpenCL WG would be happy to see this upstreamed.

https://github.com/KhronosGroup/SPIR/tree/spir_20_provisional

Sameer.

_______________________________________________
cfe-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits

Reply via email to