search for: split_low

...certain discrete number of i32 values. That's a problem. If <vscale x 1 x i32> ends up having one element, and <vscale x 2 x i32> also has one (= 2 * 0.5) element, then that's wrong: the latter type must have twice as many elements as the former (one example where this matters: split_low / split_high / concat shuffle patterns). The second option, a vector with *zero* elements, is just as wrong if not worse. It's not that a correct legalization exists but it's too annoying to implement, or that one might exist but I'm too lazy to work it out. We're also not running...

...can be one of the following (with examples of the equivalent <4 x i32> shuffles): splat - Splat element 0 of the first operand. (<0, 0, 0, 0>) reverse - Reverse the elements of the first operand (<3, 2, 1, 0>) concat - Concatenate the two operands (<0, 1, 2, 3, 4, 5, 6, 7>) split_low - Return the low half of the first operand (<0, 1>) split_high - Return the high half of the first operand (<2, 3>) zip_low - Zip together the low halves of the two operands (<0, 4, 1, 5>) zip_high - Zip together the high halves of the two operands (<2, 6, 3, 7>) unzip_even...

Hi all, On Tue, 7 Apr 2020 at 11:04, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Tue, 7 Apr 2020 at 09:30, Kai Wang via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > LMUL = 1 LMUL = 2 LMUL = 4 LMUL = 8 > > int64_t | vscale x 1 x i64 | vscale x 2 x i64 | vscale x 4 x i64 | vscale x 8 x i64