search for: clcreatekernel

...uld be parameterised by only two (more or less) parameters: bitness (32/64) and endianness (little/big). How one can even guarantee e.g. that a calling convention for NVIDIA GPUs is appropriate for ATI GPUs? So using calling conventions too early on (e.g. between invoking the clBuildProgram() and clCreateKernel() API functions) is a path to implementation divergence, rather than standardisation. From: Nick Lewycky [mailto:nlewycky at google.com] Sent: 17 December 2010 22:16 > > If that's not enough, could you swing it around and maintain single > > named metadata node with a list of fu...

On Fri, Dec 17, 2010 at 04:21:18PM -0500, David Neto wrote: > However we record the fact that a function is a kernel, the mechanism > should handle the case of a kernel calling another kernel. > Recall that a kernel called by another kernel behaves more like a > regular function. For example it doesn't have workspace iteration > automatically applied to it; rather it just

...tion with a postfix and > look up the metadata, there's no second phase of then searching through a list > to find the name of the function it's interested in. We've taken a different view on this. At the moment, I can think of 3 cases when kernel information can be required: a) clCreateKernel() is called with a kernel function name. The compiler needs to look-up metadata for this particular function, because if the function is not a kernel the user must get an CL_INVALID_KERNEL_NAME error. In this case, your approach is superior because you don't have to search the list (or about...