<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - piglit spec/egl_khr_create_context/valid debug flag gles* fail" href="https://bugs.freedesktop.org/show_bug.cgi?id=91044#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - piglit spec/egl_khr_create_context/valid debug flag gles* fail" href="https://bugs.freedesktop.org/show_bug.cgi?id=91044">bug 91044</a> from <a class="email" href="mailto:stu_dby@126.com" title="Boyan Ding <stu_dby@126.com>"> Boyan Ding</a> <pre>(In reply to Emil Velikov from <a href="show_bug.cgi?id=91044#c1">comment #1</a>) > As Intel is a Khronos member, you should have access to the SVN repo/history > for the exact details. I'd assume that it would be the better option. Sorry if I caused confusion, but I'm not affiliated with Intel (or any other Khronos member). So I seem not able to access the spec history. I tried simply removing the non-OpenGL check, but it breaks another piglit test, namely spec/egl_khr_create_context/invalid flag gles, giving EGL_BAD_MATCH instead of EGL_BAD_ATTRIBUTE in some cases (I guess when the flag given is valid for OpenGL but not ES). And I saw that test was updated against version 15 of EGL_KHR_create_context_spec (commit 5f668b1 [1]). The comment there is explains /* According to the EGL_KHR_create_context spec, version 15, there * exists exactly one valid flag for OpenGL ES contexts: the debug * flag. * If the EGL_CONTEXT_OPENGL_DEBUG_BIT_KHR flag bit is set in * EGL_CONTEXT_FLAGS_KHR, then a <debug context> will be created. * [...] This bit is supported for OpenGL and OpenGL ES contexts. */ So it seems allowing EGL_CONTEXT_OPENGL_DEBUG_BIT_KHR in OpenGL ES is more reasonable. If so, I'll work out a patch and send it to the ML. [1] <a href="http://cgit.freedesktop.org/piglit/commit/?id=5f668b118fed374a16d21ea1c0b2e82c0b658cc5">http://cgit.freedesktop.org/piglit/commit/?id=5f668b118fed374a16d21ea1c0b2e82c0b658cc5</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>