krasimir added a comment. In D103615#2858433 <https://reviews.llvm.org/D103615#2858433>, @bmahjour wrote:
> In D103615#2852430 <https://reviews.llvm.org/D103615#2852430>, @krasimir > wrote: > >> I'm unfamiliar with the altivec API. What's a reasonable source code update >> that preserves the current default behavior `-altivec-src-compat=mixed` >> under `-altivec-src-compat=xl`, i.e., under `-altivec-src-compat=xl` how >> would we compare vector bool or vector pixel to produce a vector? > > For `vector bool` comparison one could use `vec_cmpeq` and `vec_compne` (see > https://www.ibm.com/docs/en/xl-c-and-cpp-linux/16.1.1?topic=functions-vec-cmpeq). > However, `vec_cmp*` interfaces do not currently support `vector pixel`. Do > you have a concrete use case for comparing `vector pixel`s? If so I think we > should consider adding corresponding overloads to `altivec.h`. Thank you! I don't have a use case for comparing `vector pixels`. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D103615/new/ https://reviews.llvm.org/D103615 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
