[Bug 109081] [bisected] [HSW] Regression in clipping.user_defined.clip_* vulkancts tests

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=109081

--- Comment #9 from Timothy Arceri <t_arceri at yahoo.com.au> ---
(In reply to Kenneth Graunke from comment #8)
> (In reply to Timothy Arceri from comment #7)
> > > 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
> > https://patchwork.freedesktop.org/patch/263442/ 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?

I tried that but last time I checked it resulted in more hurt then help, like
most optimisations its a bit of a trade off when and where its called.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20181219/fc1f5897/attachment.html>