From: "Frank Ch. Eigler" <fche@redhat.com>
To: Shrirang Khishti <shrirangk@KPITCummins.com>
Cc: cgen@sources.redhat.com
Subject: Re: Regarding simulator porting using CGEN
Date: Thu, 13 Oct 2005 19:14:00 -0000 [thread overview]
Message-ID: <20051013191400.GD17481@redhat.com> (raw)
In-Reply-To: <4A1BE23A7B777442B60F4B4916AE0F1307FE2B7D@sohm.kpit.com>
Hi -
Shrirang Khishti wrote:
> [...] I am working on porting binutils,simulator for a new
> target. I have successfully ported assembler, disassembler using
> CGEN . Now I want to port simulator for my target using the same
> cgen CPU files. [...]
The process is roughly as follows.
First, decide whether you want to end up with a gdb- or sid-based
simulator, since cgen can generate decoding kernels for either. Next,
check out the respective simulator distribution sources, and
duplicate/rename the configury / directory structure of another
cgen-based target (m32r might still work). Then, have cgen generate
the kernel for your target. Finally, write the necessary glue C or
C++ code to interface the chosen infrastructure with the kernel. This
consists mainly of boilerplate code that embodies the instruction
fetch/decode/execute loop.
- FChE
prev parent reply other threads:[~2005-10-13 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 7:15 Shrirang Khishti
2005-10-13 19:14 ` Frank Ch. Eigler [this message]
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=20051013191400.GD17481@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=shrirangk@KPITCummins.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).