[Webkit-unassigned] [Bug 70099] OpenCL implementation of W3C Filter Effects Master Bug

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Oct 17 10:56:29 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=70099





--- Comment #9 from Chris Marrin <cmarrin at apple.com>  2011-10-17 10:56:28 PST ---
(In reply to comment #7)
...
> The GC3D usage is no barrier. The opposite is the case. Many CL objects have objects with the same meaning in GL and can be used by OpenCL as well:
> 
> CL Buffer <-> GL Buffer
> CL Image <-> GL Texture / GL RenderBuffers
> CL Events <-> GL Sync
> CL Context <-> GL Context
> ...
> 
> (The same with D3D objects btw.).
> 
> The bigger benefit: we can use HW acceleration for SVG in the short term. This isn't possible for OpenGL right now, because we don't support GC3D on SVG. And there is still a lot to do to make SVG use GC3D IMHO.

But in order to use a hardware implementation of OpenCL without a layer, won't you have to send the filter to the hardware (usually GPU), run the OpenCL filter and then copy the resullts back to the CPU? That would have significant overhead and in many cases would cancel the benefits of doing the filtering in hardware.

> 
> But again, I don't have any opposition agains GLSL. But we can just use it for HTML at the beginning, while SVG Filters is the only standardized specification at the moment.
> 
> I'm not very familiar with OpenGL. Is the shading language used by OpenGL ES 2.0 the same like GLSL?

If you look at it as a WebGL variant of GLSL, then it is a subset of both OpenGL and OpenGL ES. There are only a few restrictions relative to GLSL ES, and GLSL ES is a pretty heavily reduced subset of GLSL.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list