Remove mac buffer impl war

include/gpu/gl/GrGLConfig.h

 
 /*
  * Copyright 2011 Google Inc.
  *
  * Use of this source code is governed by a BSD-style license that can be
  * found in the LICENSE file.
  */
 
 
 
@@ skipping 117 matching lines @@
 #endif
 
 #if !defined(GR_GL_MUST_USE_VBO)
     #define GR_GL_MUST_USE_VBO                          0
 #endif
 
 #if !defined(GR_GL_USE_NEW_SHADER_SOURCE_SIGNATURE)
     #define GR_GL_USE_NEW_SHADER_SOURCE_SIGNATURE       0
 #endif
 
-/**
- * There is a strange bug that occurs on Macs with NVIDIA GPUs. We don't
- * fully understand it. When (element) array buffers are continually
- * respecified using glBufferData performance can fall off of a cliff. The
- * driver winds up performing many DMA mapping / unmappings and chews up ~50% of
- * the core. However, it has been observed that occaisonally respecifiying the
- * buffer using glBufferData and then writing data using glBufferSubData
- * prevents the bad behavior.
- *
- * There is a lot of uncertainty around this issue. In Chrome backgrounding
- * the tab somehow initiates this behavior and we don't know what the connection
- * is. Another observation is that Chrome's cmd buffer server will actually
- * create a buffer full of zeros when it sees a NULL data param (for security
- * reasons). If this is disabled and NULL is actually passed all the way to the
- * driver then the workaround doesn't help.
- *
- * The issue is tracked at:
- * http://code.google.com/p/chromium/issues/detail?id=114865
- *
- * When the workaround is enabled we will use the glBufferData / glBufferSubData
- * trick every 128 array buffer uploads.
- *
- * Hopefully we will understand this better and have a cleaner fix or get a
- * OS/driver level fix.
- */
-#if (defined(SK_BUILD_FOR_MAC) && !GR_GL_USE_BUFFER_DATA_NULL_HINT)
-#       define GR_GL_MAC_BUFFER_OBJECT_PERFOMANCE_WORKAROUND 1
-#else
-#       define GR_GL_MAC_BUFFER_OBJECT_PERFOMANCE_WORKAROUND 0
 #endif
-
-#endif