From: Doug Evans <dje@transmeta.com>
To: "Will Newton" <will.newton@imgtec.com>
Cc: <cgen@sources.redhat.com>
Subject: Parsing mnemonic suffixes
Date: Wed, 21 Sep 2005 15:19:00 -0000 [thread overview]
Message-ID: <17201.31245.791570.379181@casey.transmeta.com> (raw)
In-Reply-To: <0D107966AF6D79418315B7C5549F4B5104E016@lemail1.le.imgtec.org>
Will Newton writes:
>
> I'm having a little trouble with getting a cgen generated assembler to
> parse multiple suffixes on a mnemonic. The instruction is specified like
> this:
>
> "add$sc$cond $reg,$reg,$reg"
>
> The operand "sc" can have a value of "S" or "" depending on whether this
> instruction sets condition flags.
> The operand "cond" can have one of a number of values ("Z", "EQ", "NE",
> "", etc.) depending on whether this instruction is conditional or not.
>
> When either $sc or $cond is used in isolation (e.g. "ADDS", "ADDEQ") the
> mnemonic is parsed correctly, when the two are used together (e.g.
> "ADDSEQ") the parse fails. Is it possible to parse an instruction like
> this with a cgen description?
I would expect this to work. I'll look into it.
next prev parent reply other threads:[~2005-09-21 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 14:10 Will Newton
2005-09-21 15:19 ` Doug Evans [this message]
2005-09-21 16:10 Will Newton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17201.31245.791570.379181@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=cgen@sources.redhat.com \
--cc=will.newton@imgtec.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).