Add a shallow command buffer flush that doesn't glFlush

content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.cc

Index: content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.cc
diff --git a/content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.cc b/content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.cc
index 2c26f2a827fa49c1e8b18c5dd60f3071a291fa0f..3c2d04e81385a0557d15aa60b5f599b42404442e 100644
--- a/content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.cc
+++ b/content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.cc
@@ -939,6 +939,10 @@ void WebGraphicsContext3DCommandBufferImpl::flush() {
     gl_->FreeEverything();
 }
 
+void WebGraphicsContext3DCommandBufferImpl::shallowFlushCHROMIUM() {
+  gl_->ShallowFlushCHROMIUM();

[nduca, 2012/07/18 06:13:06]

Was there a reason you couldn't say gl_->helper()->CommandBuffer::flush()?

Copy the design of WGC3DCBI::waitSyncPoint

Then you could skip all the delegation-via-GL bullcrap.

[brianderson, 2012/07/19 03:29:44]

In each of the wgc3d implementations I copied the call style of the regular
flush, which was slightly different.

wgc3Dcbi calling through GLES2Implementation results in a single thread check
and a call to GPU_CLIENT_LOG.

wgc3Dipcbi using the delegation macro calls a ClearContext member function for
what looks like debugging purposes.

+}
+
 DELEGATE_TO_GL_4(framebufferRenderbuffer, FramebufferRenderbuffer,

[nduca, 2012/07/18 06:13:06]

Who is advertising the extension as being supported? Look for some of the other
extensions on the wgc3d interface and then grep fro them to see how we typically
advertise extensions.

[brianderson, 2012/07/19 03:29:44]

It is advertised with other client-side-only extensions in
gles2_implementation.cc.

                  WGC3Denum, WGC3Denum, WGC3Denum, WebGLId)