e0ad2af691
While "skip measurements mode" is super useful for test coverage, i've come to discover it's trade-offs. It still calls back-end to actually codegen the target assembly, and that is what is taking 80%+ of the time regardless of whether or not we skip the measurements. On the other hand, just being able to see that exegesis can come up with a snippet to measure something, is already very useful, and takes maybe a second for a all-opcode sweep. Reviewed By: gchatelet Differential Revision: https://reviews.llvm.org/D140702
4 lines
225 B
ArmAsm
4 lines
225 B
ArmAsm
# RUN: llvm-exegesis -mtriple=powerpc64le-unknown-linux-gnu -mcpu=pwr8 --benchmark-phase=assemble-measured-code -mode=latency -opcode-name=SELECT_I8 2>&1 | FileCheck %s
|
|
|
|
CHECK: Unsupported opcode: isPseudo/usesCustomInserter
|