This is also a bug. The VK[1/2/4/8/16]PAIR here should be VK[1/2/4/8/16]Pair which has its
custom PrintMethod and ParserMatchClass. However we don't have any instructions using vvvv
and ModR/M.REG field so this issue is not exposed.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Unit Tests
Time | Test | |
---|---|---|
3,260 ms | x64 debian > libarcher.races::task-dependency.c | |
770 ms | x64 debian > libomp.lock::omp_init_lock.c |
Event Timeline
Comment Actions
Change VK1PAIR to VK1Pair may be reasonable. (keep same with other xxRegisterEncodingFromString for future ISA.)
lib/Target/X86/X86RegisterInfo.td:629:def VK1PAIR : RegisterClass<"X86", [untyped], 16, (add KPAIRS)> {let Size = 32;}
lib/Target/X86/X86InstrInfo.td:817:def VK1Pair : RegisterOperand<VK1PAIR, "printVKPair"> {
Comment Actions
I think it is fine to remove it. Tablegen will issue an error if a new instruction is added. At that point its easy to add back.