I tried to run the filter in my nvidia card and it is very slow and crashes sometimes (invalid command queue, i.e. something really bad happened). Besides the fact that the cl_process function should accept a size_t instead of a long, I couldn't find any other problems but the problem persists. Can you give another look at the patch? Victor On Wed, Jan 22, 2014 at 12:41 PM, Daniel Sabo <danielsabo@xxxxxxxxx> wrote: > It is also possible to call gegl_cl_has_extension("cl_khr_fp64") to > check for double support and then pick which kernal source string to > build at runtime. But unless it actually needs a double I would avoid > it, double will be slower pretty much everywhere, CPU included. (And > if it *does* need double precision you probably shouldn't run the > OpenCL version on devices that don't support it.) _______________________________________________ gegl-developer-list mailing list List address: gegl-developer-list@xxxxxxxxx List membership: https://mail.gnome.org/mailman/listinfo/gegl-developer-list