<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Linking fails when not writing gl_Position." href="https://bugs.freedesktop.org/show_bug.cgi?id=83380#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Linking fails when not writing gl_Position." href="https://bugs.freedesktop.org/show_bug.cgi?id=83380">bug 83380</a> from <a class="email" href="mailto:lemody@gmail.com" title="Tapani Pälli <lemody@gmail.com>"> Tapani Pälli</a> <pre>Huh I did not realize that desktop and ES specs treat this subject in a slightly different way. What I can tell from GLSL ES spec is that it is not mandatory to write gl_Position (?) At least by these paragraphs: --- 8< --- GLSL ES spec 1.0.17 says in 7.1 Vertex Shader Special Variables section: "The value of gl_Position is undefined if a vertex shader is executed and does not write gl_Position." AND 10.13 gl_Position "Is it an error if the vertex shader doesn't write to gl_Position? Whether a shader writes to gl_Position cannot always be determined e.g. if there is dependence on an attribute. Option 1: No it is not an error. The behavior is undefined in this case. Development systems should issue a warning in this case but the on-target compiler should not have to detect this. RESOLUTION: No error (option 1). The nature of the undefined behavior must be specified." --- 8< ---</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>