search for: err_as_qualified_auto_decl

...re already being used this way to a certain extent in the targets (X86 uses 256 -> GS, 257 -> FS). And I think 256 'standard' address spaces should be enough, but I'm happy to be proven wrong :) > What do I think your patch should look like? It's true that the > diag::err_as_qualified_auto_decl is inappropriate for OpenCL when it's > the __local addres space. > > But we need to implement the semantics somehow. Conceptually I think > of it as a CL source-to-source transformation that lowers > function-scope-local-address-space variables into a more primitive > form....

...en wrong :) > [Villmow, Micah] This would be very beneficial to define these. The only main issue is the default address space. In OpenCL it is private, in LLVM, it is closer to global than private. > > What do I think your patch should look like? It's true that the > > diag::err_as_qualified_auto_decl is inappropriate for OpenCL when > it's > > the __local addres space. > > > > But we need to implement the semantics somehow. Conceptually I think > > of it as a CL source-to-source transformation that lowers > > function-scope-local-address-space variables int...

....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, David Neto wrote: >> > What do I think your patch should look like?  It's true that the >> > diag::err_as_qualified_auto_decl is inappropriate for OpenCL when >> it's >> > the __local addres space. >> > >> > But we need to implement the semantics somehow.  Conceptually I think >> > of it as a CL source-to-source transformation that lowers >> > function-scope-local-add...

...gt; >> Subject: Re: [LLVMdev] [cfe-dev] OpenCL support > >> > >> Hi David, > >> > >> On Mon, Dec 06, 2010 at 11:14:42AM -0500, David Neto wrote: > >> > What do I think your patch should look like?  It's true that the > >> > diag::err_as_qualified_auto_decl is inappropriate for OpenCL when > >> it's > >> > the __local addres space. > >> > > >> > But we need to implement the semantics somehow.  Conceptually I > think > >> > of it as a CL source-to-source transformation that lowers > &gt...