public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: "æ± ç¿" <dam_wang@hotmail.com>
Cc: sid@sources.redhat.com
Subject: Re: can sid use CGEN-defined cpu as a simulat component
Date: Thu, 19 Sep 2002 07:50:00 -0000	[thread overview]
Message-ID: <20020919105019.B2755@redhat.com> (raw)
In-Reply-To: <F44xbYiMCIqtQvAauNj0002a57e@hotmail.com>; from dam_wang@hotmail.com on Thu, Sep 19, 2002 at 02:19:44PM +0000

[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]

Hi -

On Thu, Sep 19, 2002 at 02:19:44PM +0000, æ± ç¿ wrote:
> [...]
> What I want to do now is to build an CGEN-CPU componet, such as an DSP CPU. 
> After read the CDK and the source file,I think the process of building it 
> is:
> 
> 1, write the .cpu file in CGEN's RTL( fortunately I know how to do now ^-^)
> 2, make cgen-all under the sid build tree
> 3, hand writing files 
>   * write a file like m32rbf.cxx and m32rbf.h in m32r, (is it what you mean 
> in last letter u giveme? However, I have no imformation about how to write 
> this file.)
>   * mordify the compCGEN.cxx file under ../cgen-cpu.I see in this file some 
> CPU-dependent imformation:
>  [...]
> 
> Are these right? If so, could you please offer me more information about 
> how to do this hand writing or where to get the guide document?

You're on the right track.  We do not have a public document that lists
all the necessary steps, but one general approach is to completely
duplicate/rename an existing port (m32r as a simple case), then hack on
it until it works for your port.  Another approach, for prototyping only,
is to replace the guts of an existing port, so the old name and build
infrastructure (Makefiles, configure*, compCGEN.cxx, etc.) can remain
unmodified.


- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

           reply	other threads:[~2002-09-19 14:50 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <F44xbYiMCIqtQvAauNj0002a57e@hotmail.com>]

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=20020919105019.B2755@redhat.com \
    --to=fche@redhat.com \
    --cc=dam_wang@hotmail.com \
    --cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).