<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> Eero Tamminen</a> changed <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> <table border="1" cellspacing="0" cellpadding="8"> <tr> <th>What</th> <th>Removed</th> <th>Added</th> </tr> <tr> <td style="text-align:right;">Status</td> <td>RESOLVED </td> <td>VERIFIED </td> </tr></table> <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#c25">Comment # 25</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:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> Eero Tamminen</a> <pre>(In reply to Kenneth Graunke from <a href="show_bug.cgi?id=97532#c22">comment #22</a>) > Just discovered another reason I didn't notice this bug: this shader is only > used for the loading screen. If you run it with -skip_load_frames, it works > fine. Thanks, I didn't know about that, it indeed works fine. (In reply to Kenneth Graunke from <a href="show_bug.cgi?id=97532#c23">comment #23</a>) > Created <a href="attachment.cgi?id=127853" name="attach_127853" title="A patch that implements a drirc option">attachment 127853</a> <a href="attachment.cgi?id=127853&action=edit" title="A patch that implements a drirc option">[details]</a> <a href='page.cgi?id=splinter.html&bug=97532&attachment=127853'>[review]</a> [review] > A patch that implements a drirc option > > Here's a patch that implements a drirc option. Thanks, this works fine too, and the patch is much smaller than I expected! Comment added at the end of patch would need to be updated before commiting. This same override would be needed also for currently available glmark2-es2 releases (fixes for the bugs are only in glmark2 git repo). (In reply to Ian Romanick from <a href="show_bug.cgi?id=97532#c24">comment #24</a>) > (In reply to Eero Tamminen from <a href="show_bug.cgi?id=97532#c19">comment #19</a>) > > [1] Linux desktop has only handful of GLES programs (and most of them > > compositors i.e. not really using complex shaders). There could be other > > regressing cases on ChromeOS (WebGL www-pages) or Android. > > I suspect this will not be a problem for WebGL. WebGL conformance is even > more picky about such restrictions that the native API CTS. > > There have been no reports of Android applications failing due to this > change. Should there be any problems with Android applications, they will > be handled on a case-by-case basis. With the GLB workaround option available, this is fine for me. If there are other buggy proprietary apps, Kenneth's patch can be applied. -> Verified --- We just don't know whether there are other problematic apps: * Different WebGL scripts on random www-pages aren't conformance tested. They can have this bug if they're developed against Browsers & 3D driver versions that haven't (had) this check * AFAIK there aren't Android devices shipping with Mesa 13.0 (which is the first version with this issue), so there cannot be any reports of issues yet * I didn't find (by googling) any reports of GLB 2.x failing with any other driver (and it works fine with GLES version of Intel Windows driver) * Glmark2 had the same issue and nobody had noticed anything on Linux or Android with other drivers (at least I was the first one to file a bug about it)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>