[PATCH] D65683: MVT: Add v3i16/v3f16 vectors
Matt Arsenault via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Sun Aug 4 09:37:26 PDT 2019
arsenm added a comment.
In D65683#1613355 <https://reviews.llvm.org/D65683#1613355>, @craig.topper wrote:
> I think there's a bug in computeRegisterProperties for TypeWidenVector. For non-power2 vectors we need to go the next largest power of 2 vector. Currently its goes through the loop looking for a legal vector with more elements. For X86 it takes v3i16 all the way to v8i16. It should only take it to v4i16.
Why should it go to v4i16? I don't see that added as a legal type in x86? I only see v8i16, v16i16, and v32i16 as possible legal vectors
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D65683/new/
https://reviews.llvm.org/D65683
More information about the llvm-commits
mailing list