[RISCV] Mark vmvNr.v as implicitly using vtype

[lukel97]

This was pointed out in #118283 (comment). We cannot move these between vtype definitions as they depend on SEW and require vill to be clear.

[llvmbot]

@llvm/pr-subscribers-backend-risc-v

Author: Luke Lau (lukel97)

Changes

This was pointed out in #118283 (comment). We cannot move these between vtype definitions as they depend on SEW and require vill to be clear.

---

Full diff: https://github.com/llvm/llvm-project/pull/118414.diff

1 Files Affected:

• (modified) llvm/lib/Target/RISCV/RISCVInstrInfoV.td (+1-1)

diff --git a/llvm/lib/Target/RISCV/RISCVInstrInfoV.td b/llvm/lib/Target/RISCV/RISCVInstrInfoV.td
index 8e0c4826ac00de..6506b6746b1517 100644
--- a/llvm/lib/Target/RISCV/RISCVInstrInfoV.td
+++ b/llvm/lib/Target/RISCV/RISCVInstrInfoV.td
@@ -1726,7 +1726,7 @@ foreach n = [1, 2, 4, 8] in {
   def VMV#n#R_V  : RVInstV<0b100111, !add(n, -1), OPIVI, (outs vrc:$vd),
                            (ins vrc:$vs2), "vmv" # n # "r.v", "$vd, $vs2">,
                    VMVRSched<n> {
-    let Uses = [];
+    let Uses = [VTYPE];
     let vm = 1;
   }
 }

[topperc]

LGTM

[lukel97]

I had to update the llvm-mca tests, I'm not sure why adding a use affects the number of cycles. cc @mshockwave

[preames]

I had to update the llvm-mca tests, I'm not sure why adding a use affects the number of cycles. cc @mshockwave

LGTM as well, the mca change is at least reasonable if we're modeling a new runtime dependency which wasn't previously being modeled.

[topperc]

I had to update the llvm-mca tests, I'm not sure why adding a use affects the number of cycles. cc @mshockwave

LGTM as well, the mca change is at least reasonable if we're modeling a new runtime dependency which wasn't previously being modeled.

Looking at the test. There are vsetvlis interleaved with vmv. So I assume llvm-mca is now waiting for the preceding vsetvli before it can start a vmv.