<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [bisected] [HSW] Regression in clipping.user_defined.clip_* vulkancts tests" href="https://bugs.freedesktop.org/show_bug.cgi?id=109081#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [bisected] [HSW] Regression in clipping.user_defined.clip_* vulkancts tests" href="https://bugs.freedesktop.org/show_bug.cgi?id=109081">bug 109081</a> from <a class="email" href="mailto:kenneth@whitecape.org" title="Kenneth Graunke <kenneth@whitecape.org>"> Kenneth Graunke</a> <pre>(In reply to Timothy Arceri from <a href="show_bug.cgi?id=109081#c7">comment #7</a>) > > I suspected it was something like that. I was planning to go through and > > beef up the places that handle if-statements to also handle bcsel. That > > doesn't (conceptually) seem to hard. What do you think? > > It should be fine for opt_peel_loop_initial_if() but for things like > opt_if_evaluate_condition_use() and > <a href="https://patchwork.freedesktop.org/patch/263442/">https://patchwork.freedesktop.org/patch/263442/</a> it's not really possible to > do. If that's the case, then maybe we ought to be doing peephole select optimizations (or at least the fancier versions?) later in the optimization process, after we do those other passes to clean up control flow?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>