<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [radeonsi] [bisected] reaction-game crashes with GLSL compiler error" href="https://bugs.freedesktop.org/show_bug.cgi?id=89064#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [radeonsi] [bisected] reaction-game crashes with GLSL compiler error" href="https://bugs.freedesktop.org/show_bug.cgi?id=89064">bug 89064</a> from <a class="email" href="mailto:cworth@cworth.org" title="Carl Worth <cworth@cworth.org>"> Carl Worth</a> <pre>I'm glad to hear that the bug in Reaction Quake has since been fixed. But I'm concerned to learn that the patches I wrote never landed---that's a bit distressing. For reference, it looks like my latest patch after all of the discussion is here: <a href="http://lists.freedesktop.org/archives/mesa-dev/2014-August/065087.html">http://lists.freedesktop.org/archives/mesa-dev/2014-August/065087.html</a> I'll need to track down why that was never committed, (I was probably waiting for review at the time?). And I'll also need to track down what other changes I might have in branches that never got pushed. That said, I don't think that that change to Mesa would mean that Reaction Quake with the bug would start working. It really was sending a bogus shader to Mesa, and it really was just a bug in Mesa that was causing it to be accepted as valid. (This is all based on my recollection which might not be fully accurate.) -Carl</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>