From: Andrew Cagney <cagney@gnu.org>
To: David Voit <david.voit@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: Need help at writing basic igen simulator
Date: Tue, 14 Sep 2004 22:12:00 -0000 [thread overview]
Message-ID: <41476C5D.4050209@gnu.org> (raw)
In-Reply-To: <pan.2004.09.14.21.03.59.671898@gmail.com>
If you leave this out:
> {
> /* TODO */
> }
igen should automatically generate code to throw an unimplemented
instruction exception.
> If i write the instruction identifer in hexform like this
> "8.0xe3,8.reg,16.value::::setl" igen fails with "ld-insn.c:293: assertion
> failed - word->first->last < 0" it this the correct behavior.
Hmm, forgotten that it was possible to specify hex values. Looking at
the mn10300, I think you need:
:option:::insn-specifying-widths:true
I've not tried to bring up an IGEN simulator from scratch for some years
- the onces I worked on were rewrites of existing hand written simulators.
Andrew
next prev parent reply other threads:[~2004-09-14 22:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 21:30 David Voit
2004-09-14 22:12 ` Andrew Cagney [this message]
2004-09-15 19:41 ` David Voit
[not found] ` <005001c49aef$eb8cf000$5100a8c0@monika>
2004-09-15 19:43 ` David Voit
2004-09-15 9:37 Monika Chaddha
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=41476C5D.4050209@gnu.org \
--to=cagney@gnu.org \
--cc=david.voit@gmail.com \
--cc=gdb@sources.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