From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21104 invoked by alias); 19 Dec 2002 19:34:09 -0000 Mailing-List: contact cgen-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cgen-owner@sources.redhat.com Received: (qmail 21065 invoked from network); 19 Dec 2002 19:34:07 -0000 Received: from unknown (HELO mars.net-itech.com) (24.100.100.83) by 209.249.29.67 with SMTP; 19 Dec 2002 19:34:07 -0000 Received: (qmail 14212 invoked from network); 19 Dec 2002 19:33:52 -0000 Received: from unknown (HELO satori) (192.168.12.27) by mars.net-itech.com with SMTP; 19 Dec 2002 19:33:50 -0000 Content-Type: text/plain; charset="iso-8859-1" From: David Carney Organization: Net Integration Technologies To: cgen@sources.redhat.com Subject: Re: cgen fundamentals Date: Thu, 19 Dec 2002 11:34:00 -0000 User-Agent: KMail/1.4.3 References: <200212181823.41189.dfcarney@net-itech.com> In-Reply-To: Cc: bje@redhat.com MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200212191433.48565.dfcarney@net-itech.com> X-SW-Source: 2002-q4/txt/msg00114.txt.bz2 > Hi David. Welcome. Thanks. > CGEN is a framework, in which CGEN applications run. There are a > handful of these now: an opcodes table generator, a simulator kernel > generator, and so on. If you just want to port binutils, you need > only concern yourself with generating the opcodes/* files. The GNU > binutils "opcodes" directory has Makefile fragments for other ports > (like fr30) that can be duplicated almost verbatim. These Makefile > fragment are responsible for running CGEN for you and depositing the > output files in the opcodes/ source directory. I would suggest you > focus on writing your CPU description first and then work out how to > run it from opcodes/Makefile. > > Please feel free to ask more questions on this otherwise quiet list! Oh, I will. Don't worry... :) So, basically, I define my own .cpu file and add a new target to the=20 binutils/opcodes Makefile (that'll use cgen in conjunction with my .cpu=20 file), correct? After I get cgen to properly generate files for=20 binutils/opcodes, I'll need to write my own cpu-???.* and elf32-???.* files= =20 for the binutils/bfd, right? What else will I need to do to get an assembler up and running? Thanks, Dave