[Bug 97321] Query INFO_LOG_LENGTH for empty info log should return 0
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Nov 16 20:27:20 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=97321
--- Comment #17 from Ian Romanick <idr at freedesktop.org> ---
There has been a couple weeks of discussion about this inside Khronos (see
Khronos internal bug #16110).
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?
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20161116/3f109f62/attachment.html>
More information about the intel-3d-bugs
mailing list