<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - glsl-fs-shader-stencil-export hangs forever" href="https://bugs.freedesktop.org/show_bug.cgi?id=106393#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - glsl-fs-shader-stencil-export hangs forever" href="https://bugs.freedesktop.org/show_bug.cgi?id=106393">bug 106393</a> from <a class="email" href="mailto:itoral@igalia.com" title="Iago Toral <itoral@igalia.com>"> Iago Toral</a> <pre>(In reply to Mark Janes from <a href="show_bug.cgi?id=106393#c1">comment #1</a>) > I reverted the bisected patch, and the subsequent patch enabling > shaderInt16. Mesa CI was inoperable with the spinning piglit tests. We had never seen this reported by Jenkins but I can confirm that we can reproduce the problem locally, was this test temporarily disabled or something? or could it be silently skipped due to the long run time? We sent the series to Jenkins prior to landing it in master. Anyway, we have looked into it and it seems the problem is a MOV with a Byte type: mov(8) g127<1>UB g2<32,8,4>UB These need special handling in the compiler, Chema had already found about this while adding support for 8-bit integers, we just weren't aware that the driver already had a case where Byte types were already being used... I'll talk to Chema about this but we probably already have the fix available.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>