OpenCL address space and mangling
michele.scandale at gmail.com
Wed Jul 24 09:03:57 PDT 2013
On 07/24/2013 05:36 PM, Pekka Jääskeläinen wrote:
> FWIW, we do it this way in pocl now. That is, we force known address space ids
> to the OpenCL address spaces via the fake address space map feature so the
> OpenCL C kernel compiler passes can refer to non-target-specific address spaces
> during the work group generation.
I know there is that option, but it's there only for testing purpose. It can be
a temporary workaround but not a long term solution. I think it's useful for
everybody to find and apply solutions that keep clean both design and code.
As said it would be very interesting to discuss in order to found a clean way to
represent logical address spaces independently from target address spaces so
that in the middle end this information can be exploited for language specific
Maybe a simple extension of the 'addrspace' modifier so that it can represent
either logical or physical address spaces will be fine, but we need to discuss
the implementation details and understand if it's a solution that fits the goals
in term of usability, maintainability and compatibility.
More information about the cfe-commits