[cfe-dev] OpenCL address space and mangling

[David Tweed]

| The pure solution would be the one proposed by Eli: I don't have any objection
| to this solution.
| The mangler now has a bug, so it must be fixed. The pure solution implicitly
| breaks the binary compatibility. If we do not have problem with this (so we
| consider a matter for the users to solve the problem, e.g. with a forced update
| of libraries) the right patch is to have a target independent mangling for OpenCL.

I think there's another reason for desiring a target independent mangling: a system may contain several OpenCL devices and the actual implementation of address spaces (in particular whether they're "front-end annotations only" or actually denote physically different regions of memory) may depend on the OpenCL device (with its associated backend). (In the conventional OpenCL usage it may not matter since one could postpone the address space resolution to later in the process; once you've got to process already produced SPIR I think it does.)

Cheers,
Dave

-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.

ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No:  2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No:  2548782