<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><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#c8">Comment # 8</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 <span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span></b>
<pre>(In reply to Timothy Arceri from <a href="show_bug.cgi?id=99221#c7">comment #7</a>)
<span class="quote">> I've attached dumps from unrolling the loops with the different passes. It
> doesn't look like there is any easy solution, both have the same instruction
> count it looks like the result comes down to scheduling.</span >
NIR version schedules the second last "send" worse, and it has more register
bank conflicts with "mad" instructions.
Is it possible that the patch would affect anything else besides shaders with
(non-dead) loops?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>