<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Invalid sampling of second texture in fragment shader that have two samplers with different parameters." href="https://bugs.freedesktop.org/show_bug.cgi?id=95085#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Invalid sampling of second texture in fragment shader that have two samplers with different parameters." href="https://bugs.freedesktop.org/show_bug.cgi?id=95085">bug 95085</a> from <a class="email" href="mailto:nhaehnle@gmail.com" title="Nicolai Hähnle <nhaehnle@gmail.com>"> Nicolai Hähnle</a> <pre>I think I understand now where the bug is coming from, and I'm not sure if it's a driver or an application bug :) The trace uses glVertexAttribPointer instead of glVertexAttribIPointer to set up a vertex element that will consumed by an uint GLSL variable. I kind of suspect that that should be undefined behaviour, but I haven't found a corresponding spec reference. In any case, it looks like this causes different parts of the driver and the various auxiliary tools to disagree about whether the element should be treated as an int or as a float, and some conversion happens somewhere that makes it all go wrong...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>