search for: splitvecop

...> intrinsics directly for these. > > The floating point intrinsics are trickier as they (may) have stricter > ordering constraints that is still causing issues and may need tweaking > (e.g. see PR36734). > The vector reduction intrinsics still need quite a lot of work. Apart from SplitVecOp, all legalizations are currently missing. This is only noticeable on AArch64 right now, because all other targets expand vector reductions prior to codegen. Nikita > On 09/02/2019 16:17, Sanjay Patel wrote: > > The IR update to allow vector types was here: > https://reviews.llvm.org/...

...efore the next release (assuming > > someone has the time to take on the work) - it'd be nice to have the > > SLP vectorizer emit reduction intrinsics directly for these. > > > > The vector reduction intrinsics still need quite a lot of work. Apart > > from SplitVecOp, all legalizations are currently missing. This is only > > noticeable on AArch64 right now, because all other targets expand vector > > reductions prior to codegen. > > My follow-up question, then, is this: > > What do you recommend, in terms of LLVM IR, in order to obtain t...

The IR update to allow vector types was here: https://reviews.llvm.org/D57090 ...we didn't update the docs at that time because it was not clear what the backend would do with that, but that might've changed with some of the more recent patches. On Sat, Feb 9, 2019 at 1:42 AM Craig Topper via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I don't think I understand your