Displaying 2 results from an estimated 2 matches for "trycustomparseoperand".
2013 Feb 05
2
[LLVMdev] AsmParser for backend
...matched successfully
MatchOperand_NoMatch, // operand did not match
MatchOperand_ParseFail // operand matched but had errors
};
OperandMatchResultTy MatchOperandParserImpl(
SmallVectorImpl<MCParsedAsmOperand*> &Operands,
StringRef Mnemonic);
OperandMatchResultTy tryCustomParseOperand(
SmallVectorImpl<MCParsedAsmOperand*> &Operands,
unsigned MCK);
#endif // GET_ASSEMBLER_HEADER_INFO
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130205/2c609aac/attachment.html>
2013 Feb 05
0
[LLVMdev] AsmParser for backend
...Operand_NoMatch, // operand did not match
> MatchOperand_ParseFail // operand matched but had errors
> };
> OperandMatchResultTy MatchOperandParserImpl(
> SmallVectorImpl<MCParsedAsmOperand*> &Operands,
> StringRef Mnemonic);
> OperandMatchResultTy tryCustomParseOperand(
> SmallVectorImpl<MCParsedAsmOperand*> &Operands,
> unsigned MCK);
>
> #endif // GET_ASSEMBLER_HEADER_INFO
My understanding is that this will be generated automatically
if any instruction has an operand that needs a custom parser
(i.e. one that has been defined using...