Displaying 3 results from an estimated 3 matches for "workdim".
Did you mean:
workdir
2010 Dec 20
1
[LLVMdev] [cfe-dev] Function-level metadata for OpenCL (was Re: OpenCL support)
...user program can invoke a kernel as an NDRange, i.e. with an implied
loop around it to iterate over an index space of 1 to 3 dimensions.
(This is the "big idea" of OpenCL). (The index values are available
in the function body from intrinsic functions get_work_dim() and
get_global_id(uint workdim).)
But that implied loop is only applied when directly called from the
user program. When a kernel is called from another kernel, it behaves
as a regular function call and just adopts the caller's index point.
The spec does not specify whether or how that implied loop is
represented in the IR...
2010 Dec 17
0
[LLVMdev] [cfe-dev] Function-level metadata for OpenCL (was Re: OpenCL support)
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
2010 Dec 16
4
[LLVMdev] Function-level metadata for OpenCL (was Re: OpenCL support)
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
>