Displaying 2 results from an estimated 2 matches for "matchandemitinstruct".
2015 Sep 28
3
Parse Instruction
Hi ES,
From what I understand instruction parsing is divided into two parts:
- Parsing an operand list (XXXAsmParser::ParseInstruction)
- Turning the operand list into an actual instruction
(XXXAsmParser::MatchAndEmitInstruction)
The second part does the validation (e.g. how many operands, what kind,
etc) while the first part only does the parsing. That's why I think in
the first part you have to handle all possible operand combinations
(i.e. parse the first operand, and keep parsing operands as long as you
see...
2015 Sep 28
2
Parse Instruction
Hi all,
in most of the architectures, assembly operands are comma-separated.
I would like to parse an assembly code that is space-separated and I am
having a bit of problem.
In *ParseInstruction* function, I don't know what is the easiest way to
figure out how many operands a mnemonic expected to have.
In comma-separated assembly code, it just consuming commas (while