From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15225 invoked by alias); 19 Sep 2002 14:50:21 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 15218 invoked from network); 19 Sep 2002 14:50:20 -0000 Received: from unknown (HELO touchme.toronto.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 19 Sep 2002 14:50:20 -0000 Received: from tooth.toronto.redhat.com (tooth.toronto.redhat.com [172.16.14.29]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 2CBEAB8833; Thu, 19 Sep 2002 10:50:20 -0400 (EDT) Received: (from fche@localhost) by tooth.toronto.redhat.com (8.11.6/8.11.6) id g8JEoJn26847; Thu, 19 Sep 2002 10:50:19 -0400 Date: Thu, 19 Sep 2002 07:50:00 -0000 From: "Frank Ch. Eigler" To: =?iso-8859-1?Q?=E6=B1_=E7=BF?= Cc: sid@sources.redhat.com Subject: Re: can sid use CGEN-defined cpu as a simulat component Message-ID: <20020919105019.B2755@redhat.com> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="U+BazGySraz5kW0T" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from dam_wang@hotmail.com on Thu, Sep 19, 2002 at 02:19:44PM +0000 X-SW-Source: 2002-q3/txt/msg00071.txt.bz2 --U+BazGySraz5kW0T Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1301 Hi - On Thu, Sep 19, 2002 at 02:19:44PM +0000, =E6=B1 =E7=BF wrote: > [...] > What I want to do now is to build an CGEN-CPU componet, such as an DSP CP= U.=20 > After read the CDK and the source file,I think the process of building it= =20 > is: >=20 > 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=20 > * write a file like m32rbf.cxx and m32rbf.h in m32r, (is it what you me= an=20 > in last letter u giveme? However, I have no imformation about how to writ= e=20 > this file.) > * mordify the compCGEN.cxx file under ../cgen-cpu.I see in this file so= me=20 > CPU-dependent imformation: > [...] >=20 > Are these right? If so, could you please offer me more information about= =20 > 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 --U+BazGySraz5kW0T Content-Type: application/pgp-signature Content-Disposition: inline Content-length: 232 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9ieQqVZbdDOm/ZT0RAmD1AJ9/l1ArJYNsx/dI2XLi0xk5UhdxNgCfU9D8 IF8A9VVtduufYWXe31ZTheg= =EEMp -----END PGP SIGNATURE----- --U+BazGySraz5kW0T--