From: "Will Newton" <will.newton@imgtec.com>
To: "Doug Evans" <dje@transmeta.com>
Cc: <cgen@sources.redhat.com>
Subject: RE: Parsing mnemonic suffixes
Date: Wed, 21 Sep 2005 16:10:00 -0000 [thread overview]
Message-ID: <0D107966AF6D79418315B7C5549F4B5104E01C@lemail1.le.imgtec.org> (raw)
> > 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.
Cgen/cpu/arm7.cpu does this, but I have no idea if it works. It seems
that what happens is that the mnemonic is parsed, and the trailing
suffixes as one big block are passed to cgen_parse_keyword with the
keyword table for the first suffix, e.g.:
ADDSNE -> cgen_parse_keyword is called with "SNE" and keyword table for
$sc ("", "S").
Cgen_parse_keyword then calls cgen_keyword_lookup_name with the keyword
table, which does a hash lookup of "SNE" in the keyword table. This
fails and returns the null keyword as you would expect.
Cgen_parse_keyword is then called again with "SNE" and the keyword table
for $cond ("NE", ...) which doesn't match either.
My current plan is to write a custom parse handler that doesn't use a
hash table and parses as greedily as possible.
next reply other threads:[~2005-09-21 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 16:10 Will Newton [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-20 14:10 Will Newton
2005-09-21 15:19 ` Doug Evans
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=0D107966AF6D79418315B7C5549F4B5104E01C@lemail1.le.imgtec.org \
--to=will.newton@imgtec.com \
--cc=cgen@sources.redhat.com \
--cc=dje@transmeta.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).