From: "Frank Ch. Eigler" <fche@redhat.com>
To: "æ± ç¿" <dam_wang@hotmail.com>
Cc: cgen@sources.redhat.com
Subject: Re: What CGEN-based tools are provided now?
Date: Mon, 07 Oct 2002 08:04:00 -0000 [thread overview]
Message-ID: <20021007110437.B12368@redhat.com> (raw)
In-Reply-To: <F77zYhnM6WKM6Ilh4cJ00009888@hotmail.com>; from dam_wang@hotmail.com on Mon, Oct 07, 2002 at 12:32:22PM +0000
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
Hi -
On Mon, Oct 07, 2002 at 12:32:22PM +0000, æ± ç¿ wrote:
> What tools based on CGEN are provided now? I have tried SID but I found at
> last that maybe it's not useful on my work. Are there any more tools based
> on CGEN?
Take some time to look over the opcodes/ part of binutils. That's the
area where CGEN-generated assembler/disassembler kernels are put. The
CGEN modules that do that work are all already in the cgen/*.scm files.
> [...]
> Now my work is to find a way to simulator new CPUs.I have tried SID, but
> seems to add a new CPU in it is too hard for me:firstly, it needs to
> modify some files which is machine-generated,
No, machine-generated files should be left alone.
> secondly, before the
> simulation, I need a toolchain to generate the .x file [...]
> it means to a lot of work!
It is not a simulator's job to create the executables you want to run
on it. You need a toolchain, one way or another. CGEN can help generate
the kernels of various associated tools, but there is still a considerable
amount of work involved in porting, say, gcc, gdb, and even the more minor
programs.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2002-10-07 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 5:32 姹 缈
2002-10-07 8:04 ` 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=20021007110437.B12368@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dam_wang@hotmail.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).