[all-commits] [llvm/llvm-project] 2d68a4: [llvm-exegesis] Improve test flexibility by using ...

[Pavel Kosov via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 2d68a42f084a460007b368eab191cf0ff1b976d7
      https://github.com/llvm/llvm-project/commit/2d68a42f084a460007b368eab191cf0ff1b976d7
  Author: Pavel Kosov <kpdev42 at gmail.com>
  Date:   2023-03-27 (Mon, 27 Mar 2023)

  Changed paths:
    M llvm/test/tools/llvm-exegesis/AArch64/latency-by-opcode-name.s
    M llvm/test/tools/llvm-exegesis/AArch64/lit.local.cfg
    M llvm/test/tools/llvm-exegesis/Mips/latency-GPR64.s
    M llvm/test/tools/llvm-exegesis/Mips/latency-by-opcode-name.s
    M llvm/test/tools/llvm-exegesis/Mips/lit.local.cfg
    R llvm/test/tools/llvm-exegesis/X86/lbr/lit.local.cfg
    M llvm/test/tools/llvm-exegesis/X86/lbr/mov-add.s
    A llvm/test/tools/llvm-exegesis/lit.local.cfg

  Log Message:
  -----------
  [llvm-exegesis] Improve test flexibility by using available_features

Currently, all llvm-exegesis regression tests are target-specific and
they are organized so that the entire subdirectories of
llvm/test/tools/llvm-exegesis are enabled or disabled as a whole.

After the commit e0ad2af691 ("Skip codegen" dry-run mode), at least two
kinds of tests are possible:
1) ensure that a snippet can be *generated* for the particular opcode
2) tests involving actual snippet execution inside the llvm-exegesis
   process

Thus, for the particular target subdirectory, some tests should run only
on the particular host architecture and other tests only need the target
being among LLVM_TARGETS_TO_BUILD.

This commit defines a bunch of exegesis-specific features that can be
referenced in REQUIRES, UNSUPPORTED, etc. on a test-by-test basis.

~~

Huawei RRI

Reviewed By: courbet

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