summaryrefslogtreecommitdiffstats
path: root/cc/layer_tree_host.cc
diff options
context:
space:
mode:
authorjamesr@chromium.org <jamesr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-12-08 01:29:40 +0000
committerjamesr@chromium.org <jamesr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-12-08 01:29:40 +0000
commit63487d2c29b397ad7a4ef1ef5f0d2ee8509222c6 (patch)
tree5930c11a85472f328d93f0b7c317e090435a9d08 /cc/layer_tree_host.cc
parentbbe7250added91877c9570465a407aab4a2a7e7e (diff)
downloadchromium_src-63487d2c29b397ad7a4ef1ef5f0d2ee8509222c6.zip
chromium_src-63487d2c29b397ad7a4ef1ef5f0d2ee8509222c6.tar.gz
chromium_src-63487d2c29b397ad7a4ef1ef5f0d2ee8509222c6.tar.bz2
Rename discardFramebufferEXT to discardBackbufferCHROMIUM to avoid collision with real discardFramebufferEXT
Calling the (real) discardFramebufferEXT in the compositor is a performance win, at least on tilers. However currently it can't be called because we alias the name for a different API that controls backbuffer allocation, which I don't want to change. This renames the code to make backbuffer control a completely separate API so I can pipe GL_EXT_discard_framebuffer in fully as a follow-up. Depends on https://bugs.webkit.org/show_bug.cgi?id=104316 BUG= Review URL: https://chromiumcodereview.appspot.com/11474014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@171908 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'cc/layer_tree_host.cc')
-rw-r--r--cc/layer_tree_host.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/cc/layer_tree_host.cc b/cc/layer_tree_host.cc
index 00a7b68..948e0b9 100644
--- a/cc/layer_tree_host.cc
+++ b/cc/layer_tree_host.cc
@@ -152,7 +152,7 @@ RendererCapabilities::RendererCapabilities()
, usingSetVisibility(false)
, usingSwapCompleteCallback(false)
, usingGpuMemoryManager(false)
- , usingDiscardFramebuffer(false)
+ , usingDiscardBackbuffer(false)
, usingEglImage(false)
, allowPartialTextureUpdates(false)
, maxTextureSize(0)