<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#c16">Comment # 16</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:t_arceri@yahoo.com.au" title="Timothy Arceri <t_arceri@yahoo.com.au>"> <span class="fn">Timothy Arceri</span></a>
</span></b>
<pre>(In reply to Eero Tamminen from <a href="show_bug.cgi?id=99221#c15">comment #15</a>)
<span class="quote">> Yes, with that, the float loop is unrolled and PSPom perf regression is
> fixed.
> </span >
Cool. I've pushed that fix.
commit 4b7dfd881296a542a0c08a12c27f643dabd7280c
Author: Timothy Arceri <<a href="mailto:timothy.arceri@collabora.com">timothy.arceri@collabora.com</a>>
Date: Tue Jan 3 12:03:54 2017 +1100
nir: fix loop iteration count calculation for floats
Fixes performance regression in SynMark PSPom caused by loops with float
counters not always unrolling.
For example:
for (float i = 0.02; i < 0.9; i += 0.11)
...
Reviewed-by: Jason Ekstrand <<a href="mailto:jason@jlekstrand.net">jason@jlekstrand.net</a>></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>