On Tue, Apr 8, 2014 at 3:07 PM, Bill Schmidt <wschm...@linux.vnet.ibm.com> wrote: > Hi, > > Recently I posted a patch to use vnor to invert the permute control > vector for little-endian permutes. It's come to my attention that, when > available, the vnand instruction should be used in preference to vnor > for possible future processor exploitation. This patch checks for > availability of vnand and uses it instead. It also removes earlier use > of emit_move_insn in this logic where that was not appropriate. > > Bootstrapped and tested on powerpc64le-unknown-linux-gnu with no > regressions. Is this ok for trunk? > > I would also like to backport the combined patch to the FSF 4.8 branch, > if you feel that is appropriate. Please let me know. > > Thanks, > Bill > > > 2014-04-08 Bill Schmidt <wschm...@linux.vnet.ibm.com> > > * config/rs6000/rs6000.c (rs6000_expand_vector_set): Use vnand > instead of vnor to exploit possible fusion opportunity in the > future. > (altivec_expand_vec_perm_const_le): Likewise.
Okay for trunk and 4.8. Thanks, David
