<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [regression][hang] Trine1EE hangs GPU after loading screen on Mesa3D-17.3 and later" href="https://bugs.freedesktop.org/show_bug.cgi?id=105670#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [regression][hang] Trine1EE hangs GPU after loading screen on Mesa3D-17.3 and later" href="https://bugs.freedesktop.org/show_bug.cgi?id=105670">bug 105670</a> from <a class="email" href="mailto:iive@yahoo.com" title="iive@yahoo.com">iive@yahoo.com</a> <pre>(In reply to Timothy Arceri from <a href="show_bug.cgi?id=105670#c15">comment #15</a>) > Here is a fix for drivers that use GLSL IR loop unrolling. I'm still looking > into NIR unrolling it seems there is a different bug in that pass. > > <a href="https://patchwork.freedesktop.org/patch/212881/">https://patchwork.freedesktop.org/patch/212881/</a> I can confirm that this patch fixes the bug for me. Thank you for reacting so quickly to it. Is NIR unrolling bug triggered by the same shader/trace? If so, I should not close this bug until it is fixed too.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>