Re: [Gegl-developer] Building opencl branch

[Øyvind Kolås <pippin gimp org>]

On Thu, Dec 27, 2012 at 5:25 AM, Victor Oliveira
<victormatheus gmail com> wrote:
> For now, I've been using the gegl op tool in gimp to test gegl
> operations with OpenCL.
> But it shouldn't be hard to create a simple filter using the gegl API
> and test performance.
>
> If you want to enable OpenCL, just set the GEGL_USE_OPENCL env variable [1].
>
> Also, if you build gegl with --enable-debug, you can set
> GEGL_DEBUG=opencl and get some messages about what's going on [2].
> Take care that these messages change execution time.

It makes more sense to test with GIMP 2.9 than GIMP 2.8 (the current
development version of GIMP which will be come next stable 2.10) has
moved its core storage model to actual GeglBuffers, and it is
GeglOperations doing the grunt work for compositing layers and other
core functionality in GIMP.

GIMP provides quite a few of its operations on its own, with only CPU
versions for now. OpenCL has been enabled by default during the last
bits of the GEGL development cycle.. even though it sometimes slows
things down a bit with CPU OpenCL backends, if the next tarball
release is soon, it will probably be switched off by default again.
(having it had enabled like this has allowed us to catch a few bugs
that otherwise would have gone undetected.)

Ø
-- 
«The future is already here. It's just not very evenly distributed»
                                                 -- William Gibson
http://pippin.gimp.org/                            http://ffii.org/