<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [SKL][GLES 3.1 CTS] ES31-CTS.layout_binding* GPU_HANG" href="https://bugs.freedesktop.org/show_bug.cgi?id=93312#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [SKL][GLES 3.1 CTS] ES31-CTS.layout_binding* GPU_HANG" href="https://bugs.freedesktop.org/show_bug.cgi?id=93312">bug 93312</a> from <a class="email" href="mailto:jason@jlekstrand.net" title="Jason Ekstrand <jason@jlekstrand.net>"> Jason Ekstrand</a> <pre>(In reply to Kenneth Graunke from <a href="show_bug.cgi?id=93312#c4">comment #4</a>) > I wonder if this is related to the GPU hang that Jason found a while back, > where out of bounds values in an array (of say, samplers or images) can > cause us to access an invalid surface...or a surface with a message that's > invalid for that surface (i.e. try to use the sampler on a RAW surface). Going off nothing but the test name and bug report, I think that's likely. (In reply to Marta Löfstedt from <a href="show_bug.cgi?id=93312#c5">comment #5</a>) > I am not sure, but maybe <a class="bz_bug_link bz_status_NEW " title="NEW - [SKL][GLES 3.1 CTS]ES31-CTS.compute_shader.resources-texture fail" href="show_bug.cgi?id=93407">BUG 93407</a> is related to this. It is a SKL only > failing test: ES31-CTS.compute_shader.resources-texture Again, I haven't actually looked at the test, but based on names, that seems like a reasonable guess. If it is the bug Ken is referring to above, then it comes from doing an out-of-bounds array access on an array of textures or buffers. We need to add some code to the glsl compiler that clamps array indices for arrays of external resources to range [0, size).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>