From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11516 invoked by alias); 19 Dec 2002 22:12:39 -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 11508 invoked from network); 19 Dec 2002 22:12:37 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by 209.249.29.67 with SMTP; 19 Dec 2002 22:12:37 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id gBJLk6g20179 for ; Thu, 19 Dec 2002 16:46:06 -0500 Received: from hypatia.brisbane.redhat.com (IDENT:root@hypatia.brisbane.redhat.com [172.16.5.3]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id gBJMCN226105; Thu, 19 Dec 2002 17:12:24 -0500 Received: from scooby.brisbane.redhat.com (scooby.brisbane.redhat.com [172.16.5.228]) by hypatia.brisbane.redhat.com (8.11.6/8.11.6) with ESMTP id gBJMCN507163; Fri, 20 Dec 2002 08:12:24 +1000 Received: by scooby.brisbane.redhat.com (Postfix, from userid 500) id BD7B215D; Thu, 19 Dec 2002 17:12:19 -0500 (EST) To: David Carney Cc: cgen@sources.redhat.com Subject: Re: cgen fundamentals References: <200212181823.41189.dfcarney@net-itech.com> <200212191433.48565.dfcarney@net-itech.com> From: Ben Elliston Date: Thu, 19 Dec 2002 14:12:00 -0000 In-Reply-To: <200212191433.48565.dfcarney@net-itech.com> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-q4/txt/msg00115.txt.bz2 Hi David, >>>>> "David" == David Carney writes: David> So, basically, I define my own .cpu file and add a new target David> to the binutils/opcodes Makefile (that'll use cgen in David> conjunction with my .cpu file), correct? After I get cgen to David> properly generate files for binutils/opcodes, I'll need to David> write my own cpu-???.* and elf32-???.* files for the David> binutils/bfd, right? Yes. There is relatively little work to do here (a few hundred lines of C code). You can start with an existing port and clone it. Once you get it working, you'll understand it much better and can go back and clean it up. David> What else will I need to do to get an assembler up and David> running? You'll need to write the appropriate gas/config/* files (ie. port GAS). This is mostly simplified, with a few #defines to set and some stub functions that mostly call into cgen's "binutils" runtime functions in opcodes and gas. I'd strongly recommend you follow a CGEN-based gas/binutils port closely for guidance once you get to that stage. Good luck! Ben