[all-commits] [llvm/llvm-project] d04b6d: [llvm-mca][x86] Ensure avxvnni tests actually test...

[Simon Pilgrim via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: d04b6dadb65faed3d2858ab6bd4dc06bf09e81ba
      https://github.com/llvm/llvm-project/commit/d04b6dadb65faed3d2858ab6bd4dc06bf09e81ba
  Author: Simon Pilgrim <llvm-dev at redking.me.uk>
  Date:   2025-09-11 (Thu, 11 Sep 2025)

  Changed paths:
    M llvm/lib/Target/X86/X86InstrAVX512.td
    M llvm/lib/Target/X86/X86InstrInfo.cpp
    M llvm/lib/Target/X86/X86ScheduleZnver4.td
    M llvm/test/TableGen/x86-fold-tables.inc
    M llvm/test/TableGen/x86-instr-mapping.inc
    M llvm/test/tools/llvm-mca/X86/AlderlakeP/resources-avxvnni.s
    M llvm/test/tools/llvm-mca/X86/Generic/resources-avxvnni.s
    M llvm/test/tools/llvm-mca/X86/LunarlakeP/resources-avxvnni.s
    M llvm/test/tools/llvm-mca/X86/SapphireRapids/resources-avxvnni.s
    M llvm/test/tools/llvm-mca/X86/Znver4/resources-avxvnni.s

  Log Message:
  -----------
  [llvm-mca][x86] Ensure avxvnni tests actually test the avxvnni instructions (#157892)

Noticed while checking #97271 - discovered we weren't actually testing
the vex variants of the vnni instructions in the avxvnni mca tests

Fixing this causes the znver4 results to break, because it turns out we
didn't have consistent instruction naming for the avx and avx512
variants, breaking the regex matching

So add the missing reg operand to the avx512 vnni instruction signatures
to match avx vnni



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