[llvm] [RISCV][GlobalISel] Vector Extension vadd Legalizer (PR #71400)

Jiahan Xie via llvm-commits llvm-commits at lists.llvm.org
Mon Nov 6 10:52:45 PST 2023


================
@@ -0,0 +1,14 @@
+; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
+; RUN: llc -mtriple=riscv32 -mattr=+v -stop-after=irtranslator | FileCheck %s --check-prefixes=CHECK,RV32
+; RUN: llc -mtriple=riscv64 -mattr=+v --stop-after=irtranslator | FileCheck %s --check-prefixes=CHECK,RV64
+
+define <vscale x 1 x i8> @vadd_vv_mask_nxv1i8(<vscale x 1 x i8> %va, <vscale x 1 x i8> %vb, <vscale x 1 x i1> %mask) {
----------------
jiahanxie353 wrote:

Yes, no problem!
Can you point me to the RVV calling convention? I'd like to have my `CHECK` statements conform to the calling convention. For this simplified example you gave, is it correct if I have:
```
; CHECK-LABEL: add_nxv1i8:
; CHECK:       # %bb.0:
; CHECK-NEXT:    vadd.vv v10, v8, v9
; CHECK-NEXT:    ret
```
Especially, how should I write `; CHECK-NEXT:    vadd.vv v10, v8, v9`

https://github.com/llvm/llvm-project/pull/71400


More information about the llvm-commits mailing list