<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [REGRESSION] [BISECTED] [DXVK] 1-bit booleans and Elite Dangerous shader mis-optimization" href="https://bugs.freedesktop.org/show_bug.cgi?id=111141#c20">Comment # 20</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [REGRESSION] [BISECTED] [DXVK] 1-bit booleans and Elite Dangerous shader mis-optimization" href="https://bugs.freedesktop.org/show_bug.cgi?id=111141">bug 111141</a> from <a class="email" href="mailto:s_j_newbury@yahoo.co.uk" title="Steven Newbury <s_j_newbury@yahoo.co.uk>"> Steven Newbury</a> <pre>(In reply to Jason Ekstrand from <a href="show_bug.cgi?id=111141#c10">comment #10</a>) > The undefined values appear harmless so I'm going to guess that this is > probably actually a RADV bug. Not knowing too much about RADV, how I'd go > aboug debugging it next would be to try "bisecting" nir_opt_algebraic.py by > commenting out large chunks of it and seeing if you can narrow down which > optimization triggers the problem. Fortunately, with a renderdoc trace, > it's pretty quick to test out changes (before/after shouldn't matter for the > renderdoc capture in this case) so it shouldn't take a terribly long time. > Once you've figured out which optimization is the culpret, we can see if > that optimization is buggy for some reason. If the NIR optimization looks > sound, you can try dumping the shaders out of RADV (again, I have no idea > how to do that), diff them, and see if you can figure out why it's a problem. > > For the moment, I'm going to move it over to RADV so that those people get > notified. Commenting out the bcsel@32 optimizations makes it work. I'll try enabling each one now...</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>