On Wed, Oct 12, 2011 at 03:42:12PM -0700, Richard Henderson wrote: > The generic support for vector permutation will allow for automatic > lowering to V*QImode, so all we need to add to support for these targets > is the single V16QI pattern that represents the base permutation insn. > > I'm not touching any of the other ways that the permutation insn > could be generated. After the generic support is added, I'll leave > it to the port maintainers to determine what they want to keep. I > suspect in many cases using the generic __builtin_shuffle plus some > casting in the target-specific header files would be sufficient, > eliminating several dozen builtins. > > > Ok?
I would rather change altivec_vperm_<mode> to use the new name (and also altivec_vperm_<mode>_uns). But I can live with a wrapper function for now. If we are adding permute options, can we please get the vectorizer to use optabs instead of using the targetm.vectorize.builtin_vec_perm hook? It has always struck me as a sore thumb that we have a hook that needs to return a builtin function decl (targetm.vectorize.builtin_mask_for_load also). -- Michael Meissner, IBM 5 Technology Place Drive, M/S 2757, Westford, MA 01886-3141, USA meiss...@linux.vnet.ibm.com fax +1 (978) 399-6899
