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 spaces). LLVM will reject instructions with too many operands (as
defined in the .td files).
Is this something that would work with your assembly syntax?
Cheers,
Pierre-Andre
On 28/09/15 14:21, Sky Flyer via llvm-dev wrote:> practically I cannot use a function namly *getMnemonicAcceptInfo*
> (mnemonic as input, and number of possible outputs as output), because
> there are mnemonics that accepts different number of operands! :-/
>
> Any help is highly appreciated.
>
> On Mon, Sep 28, 2015 at 10:53 AM, Sky Flyer <skylake007 at
googlemail.com
> <mailto:skylake007 at googlemail.com>> wrote:
>
> 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
> (getLexer().is(AsmToken::Comma))) and adds operands, but it's not
> the case for space...
>
> I have a dirty hack, that I manually provide such information
> (number of operands) in a function called for example
> getMnemonicAcceptInfo and with a for loop I parse the operand!!
>
> What would you suggest for parsing space-separated assembly codes
> when it comes to figuring out if a mnemonic has two operands or one?
>
> Cheers,
> ES
>
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20150928/15f20c93/attachment.html>