Add work around for devices/API filters that claim GL_KHR_debug support but don't provide functions
Review URL: https://codereview.chromium.org/1383763004
This commit is contained in:
parent
473addf176
commit
db9f66472e
@ -755,6 +755,14 @@ const GrGLInterface* GrGLAssembleGLESInterface(void* ctx, GrGLGetProc get) {
|
||||
GET_PROC_SUFFIX(PushDebugGroup, KHR);
|
||||
GET_PROC_SUFFIX(PopDebugGroup, KHR);
|
||||
GET_PROC_SUFFIX(ObjectLabel, KHR);
|
||||
// In general we have a policy against removing extension strings when the driver does
|
||||
// not provide function pointers for an advertised extension. However, because there is a
|
||||
// known device that advertises GL_KHR_debug but fails to provide the functions and this is
|
||||
// a debugging- only extension we've made an exception. This also can happen when using
|
||||
// APITRACE.
|
||||
if (!interface->fFunctions.fDebugMessageControl) {
|
||||
extensions.remove("GL_KHR_debug");
|
||||
}
|
||||
}
|
||||
|
||||
interface->fStandard = kGLES_GrGLStandard;
|
||||
|
Loading…
Reference in New Issue
Block a user