Reply – Re: HelloJOCL Problems on MacOSX
Your Name
or Cancel
In Reply To
Re: HelloJOCL Problems on MacOSX
— by Michael Bien Michael Bien
  I introduced the NPE regression yesterday night. Please take build 276
or later:

line 52 creates the CLCommandQueue on the fastest device. You could
choose a different one.

We saw in our test cluster that taking MAX_WORK_GROUP_SIZE as default
does not work with some drivers. Thats why most demos/tests hardcode
that value.

best regards,

On 02/09/2011 06:49 PM, ralphrmartin [via jogamp] wrote:

> Michael, thanks for taking the time to reply.
> Decreasing the element count seemed to overcome the out of memory problem.
> Howeevr, the worksize is still a problem.The MacBook Pro has both an Nvidia
> GeForce GT 330M and Intel integrated graphics; I am forcing it to use the
> former. I get two devices reported using CLInfo:
> CL_DEVICE_NAME   GeForce GT 330M   Intel(R) Core(TM) i7 CPU M 620 @ 2.67GHz
> and respectively
> So I don't really understand why that value of 256 is failing. In fact even
> a worksize as small as 2 fails. Maybe it is using the CPU instead of the
> GPU?
> If I set it to 1, I then get a different error:
> Exception in thread "main" java.lang.NullPointerException
>         at com.jogamp.opencl.CLContext.release(
>         at com.jogamp.opencl.CLContext.release(
>         at HelloJOCL.main(
> _______________________________________________
> If you reply to this email, your message will be added to the discussion below:
> To start a new topic under jogamp, email [hidden email]
> To unsubscribe from jogamp, visit