<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - GEN7: rendering issue on citra" href="https://bugs.freedesktop.org/show_bug.cgi?id=105440#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - GEN7: rendering issue on citra" href="https://bugs.freedesktop.org/show_bug.cgi?id=105440">bug 105440</a> from <a class="email" href="mailto:vadym.shovkoplias@globallogic.com" title="vadym <vadym.shovkoplias@globallogic.com>"> vadym</a> <pre>(In reply to Jason Ekstrand from <a href="show_bug.cgi?id=105440#c8">comment #8</a>) > In the two dumps you provided, there's quite a few differences. It would > help if we could narrow it down a bit and figure out which vertex shader is > causing the problem. Hopefully, it's one of the small ones. :-) > > I recommend putting a little check in try_coalesce in > nir_lower_vec_to_movs.c to look at shader->info.name return early for one > shader at a time such as: > > if (strcmp(shader->info.name, "GLSL8") == 0) > return; > > That way we can narrow it down to the exact shader that's causing problems. > From there, sometimes it's useful to narrow it down further with something > like > > if (strcmp(shader->info.name, "GLSL8") == 0) { > static int i = 0; > i++; > if (i > 8 && i < 20) > return; > } > > Until you get down to the smallest change you can manage which still > reproduces the bug. Thanks for the hint! Looks like issue is in GLSL18 shader.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>