search for: __get_work_group_local_base_addr

...st *vcpint; __local int volatile vvint; int a = A[0]; vint = a; vvint = a; int a2 = vint; int va2 = vvint; barrier(CLK_LOCAL_MEM_FENCE); A[0] = a2 + va2; } is translated to this, which does pass through Clang, with __local meaning attrib addrspace(2): extern __local void * __get_work_group_local_base_addr(void); // intrinsic void foo(__global int*A) { __local struct __local_vars_s { int vint; int *vpint; int const *vcpint; int volatile vvint; } * const __local_vars // this is a *private* variable, pointing to *local* addresses. // it's a cons...

...re troublesome on AMD GPU's when we run up to 256 work items in parallel. I would keep this in mind when attempting to define some standard way to do this. > is translated to this, which does pass through Clang, with __local > meaning attrib addrspace(2): > > extern __local void * __get_work_group_local_base_addr(void); // > intrinsic > void foo(__global int*A) { > __local struct __local_vars_s { > int vint; > int *vpint; > int const *vcpint; > int volatile vvint; > } * const __local_vars > // this is a *private* variable, pointing to *loc...

> -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Peter Collingbourne > Sent: Monday, December 06, 2010 2:56 PM > To: David Neto > Cc: cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] [cfe-dev] OpenCL support > > Hi David, > > On Mon, Dec 06, 2010 at 11:14:42AM -0500,

Hi David, On Mon, Dec 06, 2010 at 11:14:42AM -0500, David Neto wrote: > >> It > >> seems it would be a good idea to transform the code so that uses of x > >> become loads and stores from memory, and the address for that memory > >> is returned by a builtin function that itself is dependent on work > >> group ids. > >> > >> I'm