From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24746 invoked by alias); 15 Sep 2008 15:53:26 -0000 Received: (qmail 24736 invoked by uid 22791); 15 Sep 2008 15:53:25 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 15 Sep 2008 15:52:46 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m8FFqiOJ018914; Mon, 15 Sep 2008 11:52:44 -0400 Received: from pobox-3.corp.redhat.com (pobox-3.corp.redhat.com [10.11.255.67]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m8FFqi5x014174; Mon, 15 Sep 2008 11:52:44 -0400 Received: from dhcp-10-15-16-104.yyz.redhat.com (dhcp-10-15-16-111.yyz.redhat.com [10.15.16.111]) by pobox-3.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m8FFqhFc023200; Mon, 15 Sep 2008 11:52:44 -0400 Message-ID: <48CE84CB.7000604@redhat.com> Date: Mon, 15 Sep 2008 15:53:00 -0000 From: Dave Brolley User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: Steve Woloschek CC: cgen@sourceware.org Subject: Re: opc-file-path References: <1221485321.7469.34.camel@gateway.zbuda.com> In-Reply-To: <1221485321.7469.34.camel@gateway.zbuda.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cgen-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cgen-owner@sourceware.org X-SW-Source: 2008-q3/txt/msg00012.txt.bz2 Steve Woloschek wrote: > I am working on a port of a new processor core and have run into an > issue when running desc-cpu.c[c|h]. > > ./desc-cpu.scm:1038:32: In expression (opc-file-path): > ./desc-cpu.scm:1038:32: Unbound variable: opc-file-path > > It appears the scripts assume there is an '[cpu].opc' file. I noticed > that several processors in the /cpu directory do not have a .opc file. > The only one I ses is the cris.cpu file. The others are all part of archirectures that do have a .opc file. Not sure why cris doesn't have one. I've never tried to build it. > Any thoughts on how to get around this feature? > I would suggest creating a minimal .opc file. $src/cgen/cpu/i960.opc seems to be a minimal example you can clone. You can probably get rid of the CGEN_PRINT_INSN macro and keep the rest. At some point you will probably want to optimize the CGEN_DIS_HASH* macros for you particular port. I hope this helps, Dave