[all-commits] [llvm/llvm-project] 1b5f85: [RISCV] Pre-commit test case for D148735. NFC

[Craig Topper via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 1b5f8556daef5f706232f9f61129ba5f1d926709
      https://github.com/llvm/llvm-project/commit/1b5f8556daef5f706232f9f61129ba5f1d926709
  Author: Craig Topper <craig.topper at sifive.com>
  Date:   2023-04-20 (Thu, 20 Apr 2023)

  Changed paths:
    M llvm/test/CodeGen/RISCV/rvv/vsetvli-insert.ll

  Log Message:
  -----------
  [RISCV] Pre-commit test case for D148735. NFC


  Commit: 5894eec874e37d63d8b4dd3087469374fa1ff211
      https://github.com/llvm/llvm-project/commit/5894eec874e37d63d8b4dd3087469374fa1ff211
  Author: Craig Topper <craig.topper at sifive.com>
  Date:   2023-04-20 (Thu, 20 Apr 2023)

  Changed paths:
    M llvm/lib/Target/RISCV/RISCVInsertVSETVLI.cpp
    M llvm/test/CodeGen/RISCV/rvv/vsetvli-insert.ll

  Log Message:
  -----------
  [RISCV][WIP] Use vsetvli x0, x0 in more cases.

If the AVL is a virtual register defined by a vsetvli with the same
vlmax we need and the previous vsetvli we saw in the data flow also
has that vlmax, we can use the x0, x0 form when we insert a vsetvli.

Not only does this avoid an update of the VL physical register, but
it may allow doLocalPostpass to completely remove the inserted vsetvli
by rewriting the vtype of the previous vsetvli.

Differential Revision: https://reviews.llvm.org/D148735


Compare: https://github.com/llvm/llvm-project/compare/78f19d9ba5c8...5894eec874e3