<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_VERIFIED bz_closed" title="VERIFIED NOTOURBUG - Regression: GLB 2.7 & Glmark-2 GLES versions segfault due to linker precision error (259fc505) on dead variable" href="https://bugs.freedesktop.org/show_bug.cgi?id=97532#c38">Comment # 38</a> on <a class="bz_bug_link bz_status_VERIFIED bz_closed" title="VERIFIED NOTOURBUG - Regression: GLB 2.7 & Glmark-2 GLES versions segfault due to linker precision error (259fc505) on dead variable" href="https://bugs.freedesktop.org/show_bug.cgi?id=97532">bug 97532</a> from <a class="email" href="mailto:idr@freedesktop.org" title="Ian Romanick <idr@freedesktop.org>"> Ian Romanick</a> <pre>(In reply to Eero Tamminen from <a href="show_bug.cgi?id=97532#c36">comment #36</a>) > (In reply to Tomasz Figa from <a href="show_bug.cgi?id=97532#c35">comment #35</a>) > > By the way, it is not true that GLES 2.x didn't require this check, at least > > according to following thread: > > > > <a href="https://github.com/AnalyticalGraphicsInc/cesium/issues/817">https://github.com/AnalyticalGraphicsInc/cesium/issues/817</a> > > > > It refers to GLSL ES 1.00 specification > > (<a href="http://www.khronos.org/registry/OpenGL/specs/es/2.0/GLSL_ES_Specification_1">http://www.khronos.org/registry/OpenGL/specs/es/2.0/GLSL_ES_Specification_1</a>. > > 00.pdf) and quotes the following part: > [...] > > If you read it more carefully, it talks only about *used* uniforms. > > GLES 3.x is more explicit and requires that *declared* uniforms have to > match. > > > Different drivers could interpret *used* in different ways, as the match > requirement being for uniforms that are: > * declared (same as GLES 3.x) > * referred after post-processing, or > * linked after all optimizations are done For the most part, the GLSL solves this problem by requiring things that are statically referenced to match. This means rules are applied to some things that may be unnecessary, but it avoids the problem of depending on how hard a particular compiler will optimize things. > (Last one is the only state that can cause real errors, but checking also > declarations makes things easier for developers, things behave more > consistently between drivers and different compiler versions.) > > That's why I asked whether the problematic Android games actually use the > uniforms or not.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>