<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - r600 [CEDAR]: GPU stalls when running shadertoy "ladybug"" href="https://bugs.freedesktop.org/show_bug.cgi?id=105291#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - r600 [CEDAR]: GPU stalls when running shadertoy "ladybug"" href="https://bugs.freedesktop.org/show_bug.cgi?id=105291">bug 105291</a> from <a class="email" href="mailto:sroland@vmware.com" title="Roland Scheidegger <sroland@vmware.com>"> Roland Scheidegger</a> <pre>(In reply to Gert Wollny from <a href="show_bug.cgi?id=105291#c4">comment #4</a>) > The shader doesn't use many registers, even un-optimized the number is below > 100, so spilling doesn't occur and beyond that I don't see any option to > optimize it more (apart from rewriting the assembly manually and injecting > it). Which means the only thing we could suggest to someone who wants to > enjoy this shader on older hardware is to change the timeout like given > above. Hence I'm closing this as NOTABUG. Ah yes I see. I was thinking it was using too many regs because my browser used an older driver version, where translation failed due to too many temp regs (in fact nearly 1000...). But that's no longer the case with more recent driver stack. That shader really is from the "holy crap" department indeed, and the driver doesn't seem to do anything obviously wrong with it, so I agree hitting the timeout is expected (as a side note, things get really unresponsive here on my HD 5750...).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>