From: "Will Newton" <will.newton@imgtec.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: <cgen@sources.redhat.com>
Subject: RE: Gas error messages
Date: Wed, 14 Sep 2005 11:06:00 -0000 [thread overview]
Message-ID: <0D107966AF6D79418315B7C5549F4B5104DFF3@lemail1.le.imgtec.org> (raw)
> > The function is actually called "parse_byte_offset6" and is
> definitely
> > called. [...]
>
> Then the question is why is the cgen_parse_keyword function
> also called for your instruction. You may need to put a
> breakpoint on TARGET_cgen_parse_operand and work through it.
> Chances are something is wrong with your .opc/.cpu file, but
> without seeing relevant excerpts of those and a test case, I
> can't be much more specific.
The assembler I am writing supports a number of addressing modes,
expressed like:
GET D0.0,[D0.1+D0.2] ; D0.0 <- mem[base(D0.1)+offset(D0.2)]
GET D0.0,[D0.1+#20] ; D0.0 <- mem[base(D0.1)+offset(20)]
I have specified these a separate instrucions, e.g.:
(dni ...
"GET $DataReg1,[$DataReg2+$DataReg3]"
...
)
(dni ...
"GET $DataReg1,[$DataReg2+#$Immed]"
...
)
The immediate form is parsed by my custom parser, which returns it's
error message. However, it seems that cgen goes on to attempt to parse
the immediate as a register name, which fails with "unrecognized
keyword". Is there a way to control this behaviour? Once I have hit the
hash I would like to treat the value as always an immediate.
next reply other threads:[~2005-09-14 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 11:06 Will Newton [this message]
2005-09-14 13:59 ` Dave Brolley
-- strict thread matches above, loose matches on Subject: below --
2005-09-13 16:09 Will Newton
2005-09-13 16:17 ` Frank Ch. Eigler
2005-09-13 14:51 Will Newton
2005-09-13 14:56 ` Frank Ch. Eigler
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=0D107966AF6D79418315B7C5549F4B5104DFF3@lemail1.le.imgtec.org \
--to=will.newton@imgtec.com \
--cc=cgen@sources.redhat.com \
--cc=fche@redhat.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).