forked from OSchip/llvm-project
[MC] Reset the MCInst in the matcher function before adding opcode/operands.
On X86, the Intel asm parser tries to match all memory operand sizes when none is explicitly specified. For LEA, which doesn't really have a memory operand (just a pointer one), this results in multiple successful matches, one for each memory size. There's no error because it's same opcode, so really, it's just one match. However, the tablegen'd matcher function adds opcode/operands to the passed MCInst, and this results in multiple duplicated operands. This commit clears the MCInst in the tablegen'd matcher function. We sometimes clear it when the match failed, so there's no expectation of keeping the previous content anyway. Differential Revision: http://reviews.llvm.org/D6670 llvm-svn: 224347
This commit is contained in:
parent
1944a8cd04
commit
0dc1979293
|
@ -24,3 +24,6 @@ vmovdqa [rax], ymm0
|
|||
|
||||
// CHECK: vaddps (%rax), %zmm1, %zmm1
|
||||
vaddps zmm1, zmm1, [rax]
|
||||
|
||||
// CHECK: leal 1(%r15d), %r9d
|
||||
lea r9d, [r15d+1]
|
||||
|
|
|
@ -2965,6 +2965,7 @@ void AsmMatcherEmitter::run(raw_ostream &OS) {
|
|||
OS << " continue;\n";
|
||||
OS << " }\n";
|
||||
OS << "\n";
|
||||
OS << " Inst.clear();\n\n";
|
||||
OS << " if (matchingInlineAsm) {\n";
|
||||
OS << " Inst.setOpcode(it->Opcode);\n";
|
||||
OS << " convertToMapAndConstraints(it->ConvertFn, Operands);\n";
|
||||
|
|
Loading…
Reference in New Issue