Is it not important that the name corresponds to intrisic?

hi
As the intrisic name of WHILEWR_PXX_S is used llvm.aarch64.sve.whilewr.s.nx4i1 in test file CodeGen/AArch64/sve2-intrinsics-contiguous-conflict-detection.ll, it is a bit strange as we use nxv4i1 for <vscale x 4 x i1> usually.
So I also try the name @llvm.aarch64.sve.whilerw.s and @llvm.aarch64.sve.whilewr.s.nxv4i2.p0 for that, it seems they are all works. (https://gcc.godbolt.org/z/5YP1fz4Tr)

So Is it not important that the name corresponds to intrisic?

As the matched pattern, it seems a typo for the intrinsic name in test file sve2-intrinsics-contiguous-conflict-detection.ll

multiclass sve2_int_while_rr<bits<1> rw, string asm, string op> {
def _B : sve2_int_while_rr<0b00, rw, asm, PPR8>;
def _H : sve2_int_while_rr<0b01, rw, asm, PPR16>;
def _S : sve2_int_while_rr<0b10, rw, asm, PPR32>;
def _D : sve2_int_while_rr<0b11, rw, asm, PPR64>;

def : SVE_2_Op_Pat<nxv16i1, !cast(op # _b), i64, i64, !cast(NAME # _B)>;
def : SVE_2_Op_Pat<nxv8i1, !cast(op # _h), i64, i64, !cast(NAME # _H)>;
def : SVE_2_Op_Pat<nxv4i1, !cast(op # _s), i64, i64, !cast(NAME # _S)>;
def : SVE_2_Op_Pat<nxv2i1, !cast(op # _d), i64, i64, !cast(NAME # _D)>;
}