From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2433 invoked by alias); 9 Mar 2009 21:32:20 -0000 Received: (qmail 2424 invoked by uid 22791); 9 Mar 2009 21:32:19 -0000 X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: sourceware.org Received: from c60.cesmail.net (HELO c60.cesmail.net) (216.154.195.49) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 09 Mar 2009 21:32:13 +0000 Received: from unknown (HELO webmail2) ([192.168.1.183]) by c60.cesmail.net with ESMTP; 09 Mar 2009 17:32:12 -0400 Received: from 83-244-211-66.cust-83.exponential-e.net (83-244-211-66.cust-83.exponential-e.net [83.244.211.66]) by webmail.spamcop.net (Horde MIME library) with HTTP; Mon, 09 Mar 2009 17:32:30 -0400 Message-ID: <20090309173230.n3xz1r5o8wkwg84s-nzlynne@webmail.spamcop.net> Date: Mon, 09 Mar 2009 21:32:00 -0000 From: Joern Rennecke To: insight@sourceware.org Cc: Richard Stuckey Subject: Re: Where are the sources for insight 6.8? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.1.4) Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2009-q1/txt/msg00025.txt.bz2 > I've never noticed that before! I use gdb's release method when doing > the release, though, so I wonder if that directory is being excluded > from gdb or if there is some sort of a bug w.r.t. to handling insight > in the release process makefiles. naked-cpu is part of the gdb-support module, which in turn is part of the insight module. I've now created insight_6_8-branchpoint and insight_6_8-branch to cover all of the insight module. Release-generated files are not in there, though. I tagged / branched arc-insight_6_8-branchpoint and arc-insight_6_8-branch off there, but I also added naked-cgen to that tag/branch because it is needed in order to re-generate the cgen-generated files. So far, I've checked the code for the stand-alone ARCompact simulator on that branch.