search for: functionqualifi

...rnel/non-kernel case just by the linkage attribute. It might be a little unclean / unorthogonal, but I think it would be ok. (There are also other minor differences, e.g. the behaviour of a function-scope-local-addr-space variable in a nested kernel is implementation-defined. See the Notes in the functionQualifiers reference.) david References http://www.khronos.org/registry/cl/sdk/1.1/docs/man/xhtml/functionQualifiers.html http://www.khronos.org/registry/cl/sdk/1.1/docs/man/xhtml/clEnqueueNDRangeKernel.html http://www.khronos.org/registry/cl/sdk/1.1/docs/man/xhtml/local.html

On 16 December 2010 14:33, Peter Collingbourne <peter at pcc.me.uk> wrote: > On Thu, Dec 16, 2010 at 06:16:25PM -0000, Anton Lokhmotov wrote: > > Mike Gist wrote: > > > You could also consider placing all kernel functions in a 'kernel' > > > section, or adding a function attribute for kernels. > > Unlike in Clang, function attribute bit-fields in

On Thu, Dec 16, 2010 at 06:16:25PM -0000, Anton Lokhmotov wrote: > Mike Gist wrote: > > You could also consider placing all kernel functions in a 'kernel' > > section, or adding a function attribute for kernels. > Unlike in Clang, function attribute bit-fields in LLVM are pretty crowded > (only couple of bits are unused?). Besides, we do not want to represent >