[all-commits] [llvm/llvm-project] b6515a: [AArch64] Align 0-cycle reg-mov model of GPR64, GP...

[Tomer Shafir via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: b6515ae6843d6383c73efa3ac29ceb11c8858faf
      https://github.com/llvm/llvm-project/commit/b6515ae6843d6383c73efa3ac29ceb11c8858faf
  Author: Tomer Shafir <tomer.shafir8 at gmail.com>
  Date:   2025-06-28 (Sat, 28 Jun 2025)

  Changed paths:
    M llvm/lib/Target/AArch64/AArch64Features.td
    M llvm/lib/Target/AArch64/AArch64InstrInfo.cpp
    M llvm/lib/Target/AArch64/AArch64Processors.td
    A llvm/test/CodeGen/AArch64/arm64-zero-cycle-regmov-gpr.ll
    R llvm/test/CodeGen/AArch64/arm64-zero-cycle-regmov-gpr32.ll

  Log Message:
  -----------
  [AArch64] Align 0-cycle reg-mov model of GPR64, GPR32 reg classes (#146051)

Aligns 0-cycle register MOV model of GPR64 and GPR32 register classes to
that of FPR64 and FPR32 resolved in:
https://github.com/llvm/llvm-project/pull/144152.

- Splits `FeatureZCRegMove` into `FeatureZCRegMoveGPR64` and
`FeatureZCRegMove32` and fix Apple processors and `AArch64InstrInfo`
accordingly
- Aligns the test `arm64-zero-cycle-regmov-gpr.ll` to the FPR one

The target feature name change is effectively a breaking change. The
absolute most of users shouldn't use `-mzcm` directly, so I think it
should be ok to make an immediate switch, unless this doesn't align with
the conventions in this project. The patch adds a release note for that.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications