From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14712 invoked by alias); 30 Jan 2006 17:21:35 -0000 Received: (qmail 14704 invoked by uid 22791); 30 Jan 2006 17:21:34 -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, 30 Jan 2006 17:21:33 +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 k0UHLRJF023155; Mon, 30 Jan 2006 12:21:27 -0500 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 k0UHLL117174; Mon, 30 Jan 2006 12:21:21 -0500 Received: from [172.16.14.227] (IDENT:ZXOk/bOTSzrwpQC1TKv1FH3NLl89Oazx@topaz.toronto.redhat.com [172.16.14.227]) by pobox.toronto.redhat.com (8.12.8/8.12.8) with ESMTP id k0UHLKje010318; Mon, 30 Jan 2006 12:21:21 -0500 Message-ID: <43DE4B10.8090800@redhat.com> Date: Mon, 30 Jan 2006 17:21:00 -0000 From: Dave Brolley User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) MIME-Version: 1.0 To: Hans-Peter Nilsson CC: cgen@sourceware.org, bje@gcc.gnu.org Subject: Re: [RFA:] Fix breakage of manually building SID CPU References: <200601230331.k0N3V4LA010225@ignucius.se.axis.com> In-Reply-To: <200601230331.k0N3V4LA010225@ignucius.se.axis.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-Subscribe: List-Archive: List-Post: List-Help: , Sender: cgen-owner@sourceware.org X-SW-Source: 2006-q1/txt/msg00006.txt.bz2 Hans-Peter Nilsson wrote: >See dev.scm. The recentlish (within the last years) enumeration >SID-SIMULATOR, split off from SIMULATOR, isn't handled in >dev.scm, causing the cload after load-sid to error. It means my >how-to-repeat description for the SID-generator-problem with >cris.cpu at >broke with the SID-SIMULATOR introduction. I.e.: > > > >Which begs the question: how do people debug their new SID CPU >ports these days? > > I generaly clone a similar port and go from there using the Makefiles. >Maybe the fix is as simple as copying the SIMULATOR case? >A patch follows for that. It works for the guile sequence >above. With CGEN sources at the time of this writing, I no >longer get the error above or at the URL. I haven't checked >whether the generated code is correct, though. > >Ok to commit? > > The patch looks ok to me. Please go ahead and commit it. Dave