https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115683
--- Comment #8 from Richard Sandiford <rsandifo at gcc dot gnu.org> ---
(In reply to Uroš Bizjak from comment #7)
> Richi, maybe tree optimizers can perform their optimizations with
> vec_cmp{,u} and vcond_mask, and at the end provide the true coditional
> vector move (that calls "vcond{,u}") as a compound operation of these two
> operations?
Yeah, if a target can only handle a comparison by inverting the result, then
IMO the long-term outcome should be that the target doesn't provide that
comparison, and that target-independent code instead does the obvious
adjustment. At the moment (or at least, before the removal of the optabs),
every target did this internally, and the true picture was hidden from gimple.
