diff options
author | Shengchen Kan <shengchen.kan@intel.com> | 2024-03-08 20:54:33 +0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-03-08 20:54:33 +0800 |
commit | 1ca8092e87aea58f1c3752d03c20bdfc4259e409 (patch) | |
tree | 2f375b2a41d94b42abe55a11fa28d7485ef3c7a7 /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp | |
parent | d74287226ac8c144a2700ba589d34a8bebd85d0d (diff) | |
download | llvm-1ca8092e87aea58f1c3752d03c20bdfc4259e409.zip llvm-1ca8092e87aea58f1c3752d03c20bdfc4259e409.tar.gz llvm-1ca8092e87aea58f1c3752d03c20bdfc4259e409.tar.bz2 |
[X86][MC] Support encoding/decoding for APX CCMP/CTEST (#83863)
APX assembly syntax recommendations:
https://cdrdv2.intel.com/v1/dl/getContent/817241
NOTE:
The change in llvm/tools/llvm-exegesis/lib/X86/Target.cpp is for test
LLVM ::
tools/llvm-exegesis/X86/latency/latency-SETCCr-cond-codes-sweep.s
For `SETcc`, llvm-exegesis would randomly choose 1 other instruction to
test with `SETcc`, after selecting the instruction, llvm-exegesis would
check if the operand is initialized and valid, if not
`randomizeTargetMCOperand` would choose a value for invalid operand, it
misses support for condition code operand, which cause the flaky failure
after `CCMP` supported.
llvm-exegesis can choose `CCMP` without specifying ccmp feature b/c it
use `MCSubtarget` and only16/32/64 bit is considered.
llvm-exegesis doesn't choose other instructions b/c requirement in
`hasAliasingRegistersThrough`: the instruction should use GPR (defined
by `SETcc`) and define `EFLAGS` (used by `SETcc`).
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions