RESOLVED FIXED Bug 57464
Clipping in accelerated Canvas2D should be faster
https://bugs.webkit.org/show_bug.cgi?id=57464
Summary Clipping in accelerated Canvas2D should be faster
Stephen White
Reported 2011-03-30 09:20:33 PDT
The clipping in accelerated Canvas2D is not as fast as it could be. It clears the stencil buffer when removing clipping paths, when it would probably be faster to re-draw the path with a decrement stencil op.
Attachments
Patch (11.83 KB, patch)
2011-03-30 09:38 PDT, Stephen White
no flags
Patch (12.07 KB, patch)
2011-03-30 14:41 PDT, Stephen White
kbr: review+
Stephen White
Comment 1 2011-03-30 09:38:56 PDT
Kenneth Russell
Comment 2 2011-03-30 14:20:28 PDT
Comment on attachment 87552 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=87552&action=review The idea is good but the implementation needs cleanup. > Source/WebCore/platform/graphics/chromium/GLES2Canvas.cpp:72 > + Path m_path; > + AffineTransform m_transform; In WebKit style the m_ prefix isn't needed for members of structs. > Source/WebCore/platform/graphics/chromium/GLES2Canvas.cpp:81 > + , m_numClippingPaths(0) Please add a method to this struct like "bool clippingEnabled()" which does the test of m_numClippingPaths > 0. The tests strewn throughout this patch are gross and will be fragile in the long run. Even better, make the method call m_clippingPaths.size() and remove the duplicated m_numClippingPaths member entirely. > Source/WebCore/platform/graphics/chromium/GLES2Canvas.cpp:221 > + if (m_state->m_ctm.isIdentity() && !m_state->m_numClippingPaths) { Replace the test of m_numClippingPaths with a method call. > Source/WebCore/platform/graphics/chromium/GLES2Canvas.cpp:254 > + applyClipping(m_state->m_numClippingPaths > 0); Here and below, please replace the test of "m_state->m_numClippingPaths > 0" with a method call. > Source/WebCore/platform/graphics/chromium/GLES2Canvas.cpp:355 > + m_state->m_clippingPaths.append(PathAndTransform(path, m_state->m_ctm)); > + m_state->m_numClippingPaths++; This looks like replicated data. m_numClippingPaths == m_clippingPaths.size().
Stephen White
Comment 3 2011-03-30 14:34:46 PDT
Comment on attachment 87552 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=87552&action=review Thanks for the review. >> Source/WebCore/platform/graphics/chromium/GLES2Canvas.cpp:72 >> + AffineTransform m_transform; > > In WebKit style the m_ prefix isn't needed for members of structs. Fixed. >> Source/WebCore/platform/graphics/chromium/GLES2Canvas.cpp:81 >> + , m_numClippingPaths(0) > > Please add a method to this struct like "bool clippingEnabled()" which does the test of m_numClippingPaths > 0. The tests strewn throughout this patch are gross and will be fragile in the long run. Even better, make the method call m_clippingPaths.size() and remove the duplicated m_numClippingPaths member entirely. No, that won't work. m_numClippingPaths is the total number of paths, in all States. m_clippingPaths contains only the paths in the current State (see the comment in the GLES2Canvas copy constructor). >> Source/WebCore/platform/graphics/chromium/GLES2Canvas.cpp:221 >> + if (m_state->m_ctm.isIdentity() && !m_state->m_numClippingPaths) { > > Replace the test of m_numClippingPaths with a method call. Done. >> Source/WebCore/platform/graphics/chromium/GLES2Canvas.cpp:254 >> + applyClipping(m_state->m_numClippingPaths > 0); > > Here and below, please replace the test of "m_state->m_numClippingPaths > 0" with a method call. Done. >> Source/WebCore/platform/graphics/chromium/GLES2Canvas.cpp:355 >> + m_state->m_numClippingPaths++; > > This looks like replicated data. m_numClippingPaths == m_clippingPaths.size(). Nope (see above).
Stephen White
Comment 4 2011-03-30 14:41:03 PDT
Kenneth Russell
Comment 5 2011-03-30 14:45:06 PDT
Comment on attachment 87620 [details] Patch Thanks for doing the cleanups. I understand now the difference between m_clippingPaths' length and m_numClippingPaths. r=me
Stephen White
Comment 6 2011-03-30 14:50:04 PDT
Note You need to log in before you can comment on or make changes to this bug.