<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - r600_shader_from_tgsi - GPR limit exceeded - shader requires 360 registers"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105371#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - r600_shader_from_tgsi - GPR limit exceeded - shader requires 360 registers"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105371">bug 105371</a>
from <span class="vcard"><a class="email" href="mailto:mirh@protonmail.ch" title="mirh <mirh@protonmail.ch>"> <span class="fn">mirh</span></a>
</span></b>
<pre>(In reply to mirh from <a href="show_bug.cgi?id=105371#c5">comment #5</a>)
<span class="quote">> (In reply to mirh from <a href="show_bug.cgi?id=105371#c1">comment #1</a>)
> > Can confirm it fixes shader 2 and 5 of GraphicsFuzz demo
> > <a href="http://www.graphicsfuzz.com/benchmark/android-v1.html">http://www.graphicsfuzz.com/benchmark/android-v1.html</a>
> >
> > Should I wait for this (or, I dunno, some day sw fp64) to land before
> > reporting of the others "gcm_sched_late_pass: unscheduled ops" errors?
>
> Well, colour me shocked, but after building mesa-git with the last patch
> series all the tests now pass.
>
> Which is quite remarkable considering not even latest GCN closed drivers are
> compliant.</span >
This with firefox though.
Just noticed chromium 68 is still getting those errors for SETGT_DX10 and
MULADD_IEEE, and indeed fails six tests.
Nosb fixes it.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>