[LLVMdev] [PATCH] OpenCL support - update on keywords
Anton Lokhmotov
Anton.Lokhmotov at arm.com
Mon Feb 21 01:45:18 PST 2011
> > > > +enum OpenCLAddressSpace {
> > > > + OPENCL_PRIVATE = 0,
> > > > + OPENCL_GLOBAL = 1,
> > > > + OPENCL_LOCAL = 2,
> > > > + OPENCL_CONSTANT = 3
> > > > +};
> -----Original Message-----
> From: Villmow, Micah [mailto:Micah.Villmow at amd.com]
>
> Anton,
> Would there be any issue with switching the ordering of constant and
> local?
Hi Micah,
We'd rather not do that. First, this order follows the order of subsections
in 6.5 of the OpenCL specification, with global described in 6.5.1, local in
6.5.2, constant in 6.5.3; private is described in 6.5.4 but it's also the
default function-scope space which is 0. Second, we use the same order in
our (non-LLVM) GPU backend.
Best regards,
Anton.
More information about the llvm-dev
mailing list