Posted by Giovanni Idili on Nov 18, 2011; 1:32am
URL: https://forum.jogamp.org/Code-working-under-Snow-Leopard-but-not-on-Lion-tp3296875p3517627.html

After putting it away for months I am now back to fighting with this.

I posted something on the khronos boards [http://www.khronos.org/message_boards/viewtopic.php?f=28&t=4521] and David Garcia pointed me to clGetKernelWorkGroupInfo(..., CL_KERNEL_WORK_GROUP_SIZE, ...) in the C bindings (even though I do not fully understand how the kernel could influence the work group size of the device).

Question: is there something on the CLKernel object that wraps clGetKernelWorkGroupInfo? CLKernel.getWorkGroupSize(CLDevice device) looks promising, am I on the right path and if so am I supposed to use that work group size instead of the one I get as:

int localWorkSize = min(device.getMaxWorkGroupSize(), 256);  

Thanks for your support!

Best,
 
Giovanni