[all-commits] [llvm/llvm-project] f95ddf: [llvm-exegesis] Benchmark: gracefully handle lack ...

[Roman Lebedev via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: f95ddf0ee7377f6677461b791199c6ffdb489027
      https://github.com/llvm/llvm-project/commit/f95ddf0ee7377f6677461b791199c6ffdb489027
  Author: Roman Lebedev <lebedev.ri at gmail.com>
  Date:   2022-12-18 (Sun, 18 Dec 2022)

  Changed paths:
    A llvm/test/tools/llvm-exegesis/X86/latency/latency-SYSENTER.s
    M llvm/tools/llvm-exegesis/llvm-exegesis.cpp

  Log Message:
  -----------
  [llvm-exegesis] Benchmark: gracefully handle lack of configurations to run

Otherwise the progress meter would assert.


  Commit: 3ebfc88637bc34dc6ae292057203b31133b376c6
      https://github.com/llvm/llvm-project/commit/3ebfc88637bc34dc6ae292057203b31133b376c6
  Author: Roman Lebedev <lebedev.ri at gmail.com>
  Date:   2022-12-18 (Sun, 18 Dec 2022)

  Changed paths:
    M llvm/tools/llvm-exegesis/llvm-exegesis.cpp

  Log Message:
  -----------
  [NFC][llvm-exegesis] Improve `getOpcodesOrDie()`

We already have opcode name -> opcode index map, use it.
Reserve memory where appropriate.


  Commit: 8685445b3c9c6643432d24db6ffedddeb49ed8d2
      https://github.com/llvm/llvm-project/commit/8685445b3c9c6643432d24db6ffedddeb49ed8d2
  Author: Roman Lebedev <lebedev.ri at gmail.com>
  Date:   2022-12-18 (Sun, 18 Dec 2022)

  Changed paths:
    A llvm/test/tools/llvm-exegesis/X86/latency/latency-WRFSBASE.s
    M llvm/tools/llvm-exegesis/lib/X86/Target.cpp

  Log Message:
  -----------
  [llvm-exegesis][X86] Explicitly not support `WRFSBASE` opcode.

We can't serialize if for latency measurements, and when measuring uops,
it crashes so hard even `CrashRecoveryContext` doesn't stop it.

Looks like *this* was the last crasher, now `--opcode-index=-1`
succeeds for all three benchmark modes here.
At least with Duplication repetitor.


Compare: https://github.com/llvm/llvm-project/compare/93ac449369be...8685445b3c9c