topperc wrote: > > > I'm wondering why we need these intrinsics since we do not have vmv.v.v > > > and vmerge.vvm instructions for bf16. > > > > > > vmv.v.v and vmerge.vvm don't interpret the value in the elements. They work > > for integer or FP or bf16. If we don't provide the intrinsics then the user > > needs to use vreinterpret to do a vmerge or vmv.v.v operation on a vector > > of bf16. > > I know what vmerge and vmv.v.v mean, but in a similar way, does it mean we > need to add all the intrinsics for bf16 to keep consistent with other > floating-point type?
We already have load, store, vreinterpret, lmul_ext, lmul_trunc, vget, vcreate, vundefined. I file 3 issues on inconsistencies between Zvfhmin and Zvfbfmin https://github.com/riscv-non-isa/rvv-intrinsic-doc/issues/349 https://github.com/riscv-non-isa/rvv-intrinsic-doc/issues/350 https://github.com/riscv-non-isa/rvv-intrinsic-doc/issues/351 https://github.com/llvm/llvm-project/pull/101611 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
