<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - >2% perf drop in GfxBench T-Rex with "i965: disable loop unrolling in GLSL IR"" href="https://bugs.freedesktop.org/show_bug.cgi?id=99221#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - >2% perf drop in GfxBench T-Rex with "i965: disable loop unrolling in GLSL IR"" href="https://bugs.freedesktop.org/show_bug.cgi?id=99221">bug 99221</a> from <a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> Eero Tamminen</a> <pre>The commit fixes PSPom perf on all platforms where I have data (on GEN6 & GEN7 there was no clear drop on it, nor now increase, changes affected just GEN8 & GEN9). What you propose should be done about T-Rex & PSPhong: * Close this bug now, as the clear regression was fixed, or * Keep this bug open until Curro's scheduling rework lands, and/or somebody adds register bank conflict handling to Mesa ? Of latter, register bank conflict handling should be clear win (especially on older platforms), but scheduling is all about compromises, so some tests can go down while on average things improve.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>