[llvm-branch-commits] [llvm] [RISCV] Use larger copies when register tuples are aligned (PR #84455)
Luke Lau via llvm-branch-commits
llvm-branch-commits at lists.llvm.org
Tue Mar 26 07:22:52 PDT 2024
================
@@ -212,19 +185,13 @@ body: |
; CHECK-NEXT: $v7 = VMV1R_V $v14
; CHECK-NEXT: $v8 = VMV1R_V $v15
; CHECK-NEXT: $v9 = VMV1R_V $v16
- ; CHECK-NEXT: $v4 = VMV1R_V $v10
- ; CHECK-NEXT: $v5 = VMV1R_V $v11
- ; CHECK-NEXT: $v6 = VMV1R_V $v12
- ; CHECK-NEXT: $v7 = VMV1R_V $v13
- ; CHECK-NEXT: $v8 = VMV1R_V $v14
- ; CHECK-NEXT: $v9 = VMV1R_V $v15
+ ; CHECK-NEXT: $v4m2 = VMV2R_V $v10m2
+ ; CHECK-NEXT: $v6m2 = VMV2R_V $v12m2
+ ; CHECK-NEXT: $v8m2 = VMV2R_V $v14m2
; CHECK-NEXT: $v10 = VMV1R_V $v16
- ; CHECK-NEXT: $v22 = VMV1R_V $v16
- ; CHECK-NEXT: $v21 = VMV1R_V $v15
- ; CHECK-NEXT: $v20 = VMV1R_V $v14
- ; CHECK-NEXT: $v19 = VMV1R_V $v13
- ; CHECK-NEXT: $v18 = VMV1R_V $v12
- ; CHECK-NEXT: $v17 = VMV1R_V $v11
+ ; CHECK-NEXT: $v22m2 = VMV2R_V $v16m2
+ ; CHECK-NEXT: $v20m2 = VMV2R_V $v14m2
+ ; CHECK-NEXT: $v18m2 = VMV2R_V $v12m2
; CHECK-NEXT: $v16 = VMV1R_V $v10
----------------
lukel97 wrote:
Do we have a test for a copy like:
```
$v16_v17_v18_v19_v20_v21_v22 = COPY $v15_v16_v17_v18_v19_v20_v21
```
Because I think this will need to be all VMV1R_Vs. Does it already do this?
https://github.com/llvm/llvm-project/pull/84455
More information about the llvm-branch-commits
mailing list