<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#c17">Comment # 17</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:t_arceri@yahoo.com.au" title="Timothy Arceri <t_arceri@yahoo.com.au>"> Timothy Arceri</a> <pre>(In reply to <a href="mailto:ben@besd.de">ben@besd.de</a> from <a href="show_bug.cgi?id=106052#c16">comment #16</a>) > no, there were significantly more piglit shaders failing because gpu_shader5 > wasnt available in the context they requested. > > The two I fixed still didnt work after that. I'm not sure what you mean here. Isn't that a piglit issue? > > And there is one that still doesnt because it uses some mixture of > instructions that are depreciated in 150 and gpu_shader5 As I said in the gpu_shader5 bug we sometimes allow extensions to work in lower GL versions than the spec specifies. Whether we should be testing it works in via Piglit is questionable since other implementations use piglit for testing, but then again it is Mesas test suite so it's not unreasonable to do so.</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>