<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - shader-db crashes when running piglit shaders" href="https://bugs.freedesktop.org/show_bug.cgi?id=106052#c23">Comment # 23</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - shader-db crashes when running piglit shaders" href="https://bugs.freedesktop.org/show_bug.cgi?id=106052">bug 106052</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to <a href="mailto:ben@besd.de">ben@besd.de</a> from <a href="show_bug.cgi?id=106052#c20">comment #20</a>) > All it takes is > > - if (consts->GLSLVersion >= 400) > + if (consts->GLSLVersion >= 150) > extensions->ARB_gpu_shader5 = GL_TRUE; > > and everything is fine (well not everything but that is ;) You're mixing lots of different concepts. The GLSL compiler supports a number of GLSL versions (as required by the standard). Each version has its own features, and ability to be extended by various extensions. The *driver* supplies a maximum GLSL version that it supports, above which the compiler will just error out. This is all further complicated by compat vs core, in which case some extensions are not made available, and maximum versions are restricted. Using version overrides just messes everything up, of course, so any results with that should be discounted. Lastly remember that piglit also selects compat vs core depending on the GL version you request. This also factors into the various test outcomes. Piglit tests are real GL applications. You're acting like a developer, so please be succinct and precise in what the problem is. You're too focused on solutions.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>