<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - invariant qualifier is not valid for shader inputs" href="https://bugs.freedesktop.org/show_bug.cgi?id=96971#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - invariant qualifier is not valid for shader inputs" href="https://bugs.freedesktop.org/show_bug.cgi?id=96971">bug 96971</a> from <a class="email" href="mailto:kenneth@whitecape.org" title="Kenneth Graunke <kenneth@whitecape.org>"> Kenneth Graunke</a> <pre>No. The wording isn't great, but "Only variables output from a shader (including those that are then input to a subsequent shader) can be candidates for invariance." implies to me that you can only mark outputs as invariant. This would also make it match the GLSL ES 3xx rules. GLSL ES 3.20 has similar text, but also says in the issues section: "Do invariance qualifiers for declarations in the vertex and fragment shaders need to match? Option 1: Only allow invariance declarations on outputs. If a vertex shader output is declared as invariant, it implies that the corresponding input to the fragment shader is also invariant. Option 2: Specify that they must match. RESOLUTION: Only allow invariant declarations on outputs." The resolution is pretty clear there. You only get to use 'invariant' on outputs with the new rules. Are you running into an issue with the new code I implemented? Or just spec reading and wondering if we should have done something else?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>