<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Query INFO_LOG_LENGTH for empty info log should return 0" href="https://bugs.freedesktop.org/show_bug.cgi?id=97321#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Query INFO_LOG_LENGTH for empty info log should return 0" href="https://bugs.freedesktop.org/show_bug.cgi?id=97321">bug 97321</a> from <a class="email" href="mailto:idr@freedesktop.org" title="Ian Romanick <idr@freedesktop.org>"> Ian Romanick</a> <pre>There has been a couple weeks of discussion about this inside Khronos (see Khronos internal <a class="bz_bug_link bz_status_VERIFIED bz_closed" title="VERIFIED WONTFIX - [i915 XvMC] XvMCGetAttribute/XvMCSetAttribute should return 'BadMatch' for undefined attribute" href="show_bug.cgi?id=16110">bug #16110</a>). A lot of the discussion focused on which option would be least likely to be used incorrectly by developers. Since glGetProgramInfoLog takes a maxLength parameter, overruns should be unlikely. I'm still not 100% comfortable with it, but I can live with it. The conclusion is as follows: 1. In the initial state, the info log is empty. As of this writing, the spec says there is "no info log." 2. If the info log is empty, the GL_INFO_LOG_LENGTH query should return 0. 3. If maxLength passed to glGetProgramInfoLog is > 0, the buffer pointed to by infoLog will be NUL terminated even if GL_INFO_LOG_LENGTH returned 0. The spec be clarified to make this last point explicit. Guess who gets to write CTS tests to exercise all of this behavior? Yeah, I do. We should implement the behavior described by the pending spec changes. I believe this matches the expectations of the WebGL test referenced in comment #2. Tapani: Are you still available to do this?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>