From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31975 invoked by alias); 13 Oct 2005 19:14:15 -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 31965 invoked by uid 22791); 13 Oct 2005 19:14:12 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 13 Oct 2005 19:14:12 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j9DJEAS8031702 for ; Thu, 13 Oct 2005 15:14:10 -0400 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j9DJE1V04797; Thu, 13 Oct 2005 15:14:01 -0400 Received: from toenail.toronto.redhat.com (toenail.toronto.redhat.com [172.16.14.211]) by pobox.toronto.redhat.com (8.12.8/8.12.8) with ESMTP id j9DJE1oF001512; Thu, 13 Oct 2005 15:14:01 -0400 Received: from toenail.toronto.redhat.com (localhost.localdomain [127.0.0.1]) by toenail.toronto.redhat.com (8.13.4/8.13.4) with ESMTP id j9DJE00F022645; Thu, 13 Oct 2005 15:14:00 -0400 Received: (from fche@localhost) by toenail.toronto.redhat.com (8.13.4/8.13.4/Submit) id j9DJE0Bn022644; Thu, 13 Oct 2005 15:14:00 -0400 Date: Thu, 13 Oct 2005 19:14:00 -0000 From: "Frank Ch. Eigler" To: Shrirang Khishti Cc: cgen@sources.redhat.com Subject: Re: Regarding simulator porting using CGEN Message-ID: <20051013191400.GD17481@redhat.com> References: <4A1BE23A7B777442B60F4B4916AE0F1307FE2B7D@sohm.kpit.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A1BE23A7B777442B60F4B4916AE0F1307FE2B7D@sohm.kpit.com> User-Agent: Mutt/1.4.2.1i X-SW-Source: 2005-q4/txt/msg00004.txt.bz2 Hi - Shrirang Khishti wrote: > [...] I am working on porting binutils,simulator for a new > target. I have successfully ported assembler, disassembler using > CGEN . Now I want to port simulator for my target using the same > cgen CPU files. [...] The process is roughly as follows. First, decide whether you want to end up with a gdb- or sid-based simulator, since cgen can generate decoding kernels for either. Next, check out the respective simulator distribution sources, and duplicate/rename the configury / directory structure of another cgen-based target (m32r might still work). Then, have cgen generate the kernel for your target. Finally, write the necessary glue C or C++ code to interface the chosen infrastructure with the kernel. This consists mainly of boilerplate code that embodies the instruction fetch/decode/execute loop. - FChE