commit aeaf22bb0764c2a1b828d5f84f964ad77dce49b7
author Eric Karl <ericrk@google.com> Thu May 18 15:08:09 2017 -0700
committer Skia Commit-Bot <skia-commit-bot@chromium.org> Fri May 19 15:01:03 2017 +0000
tree a9b691a47eed970eb93467e1bcbe43da969c539f
parent cb9cc7086047bbbed1bd142d722f4952c94fb507

Updated workaround for Intel 6xxx clear to 0/1 bug

The previous workaround only handled the glClearColor(0,0,0,1) case,
it turns out we need to work around any glClearColor made up of entirely
0s and 1s.

R=bsalomon@google.com
Bug: 710443
Change-Id: I78a75559fc11811ad9a218436231354d66d2ad51
Reviewed-on: https://skia-review.googlesource.com/17327
Reviewed-by: Brian Salomon <bsalomon@google.com>
Commit-Queue: Eric Karl <ericrk@chromium.org>

src/gpu/gl/GrGLCaps.cpp

diff --git a/src/gpu/gl/GrGLCaps.cpp b/src/gpu/gl/GrGLCaps.cpp
index ba05316..5b6d45a 100644
--- a/src/gpu/gl/GrGLCaps.cpp
+++ b/src/gpu/gl/GrGLCaps.cpp
@@ -53,7 +53,7 @@
     fDoManualMipmapping = false;
     fSRGBDecodeDisableSupport = false;
     fSRGBDecodeDisableAffectsMipmaps = false;
-    fClearToOpaqueBlackIsBroken = false;
+    fClearToBoundaryValuesIsBroken = false;
     fDrawArraysBaseVertexIsBroken = false;
 
     fBlitFramebufferFlags = kNoSupport_BlitFramebufferFlag;
@@ -571,7 +571,7 @@
     // See http://crbug.com/710443
 #ifdef SK_BUILD_FOR_MAC
     if (kIntel6xxx_GrGLRenderer == ctxInfo.renderer()) {
-        fClearToOpaqueBlackIsBroken = true;
+        fClearToBoundaryValuesIsBroken = true;
     }
 #endif
     if (kQualcomm_GrGLVendor == ctxInfo.vendor()) {