It looks like in various places in SelectionDAG and related machinery we appear to implicitly or explicitly assume that TypeExpandInteger only applies to scalars. Does anybody know why that is? For our target (Pixel Visual Core: https://www.blog.google/products/pixel/pixel-visual-core-image-processing-and-machine-learning-pixel-2/) expanding a N-bit vector op into two (N/2)-bit vector ops is a natural way to legalize some of our vector operations, but we're finding that we need to modify a bunch of random places in the code to make it work. I'm curious if there is a cleaner way, or some big picture thing I'm missing. Thanks, -- Sean Silva -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171211/df4f6f15/attachment.html>