From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4086 invoked by alias); 24 Sep 2004 12:50:36 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 4053 invoked from network); 24 Sep 2004 12:50:33 -0000 Received: from unknown (HELO miranda.se.axis.com) (193.13.178.2) by sourceware.org with SMTP; 24 Sep 2004 12:50:33 -0000 Received: from [10.84.130.1] (ironmaiden.se.axis.com [10.84.130.1]) by miranda.se.axis.com (8.12.9/8.12.9/Debian-5local0.1) with ESMTP id i8OCoWjq022030 for ; Fri, 24 Sep 2004 14:50:32 +0200 Message-ID: <41541817.3020102@axis.com> Date: Fri, 24 Sep 2004 12:50:00 -0000 From: Orjan Friberg Organization: Axis Communications User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616 MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: Upcoming target: CRISv32 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-09/txt/msg00214.txt.bz2 I'm starting to feel pretty confident about my CRISv32 port, and would like some advice as to how to proceed. The thing is, the CRISv32 binutils port won't be submitted for another few weeks. Obviously this means that gdb for CRISv32 won't build. On the other hand, submitting it would have its benefits regarding ongoing deprecation etc, and (more importantly) I assume it will be easier to get non-architecture specific patches accepted. If submitting a non-buildable port is frowned upon, then I'd be happy to sit on it until the binutils code is in place. For the record: basically what's left at the moment are some FAILs in the most recent gdb.base/sigstep.exp and gdb.threads/schedlock.exp (problem explained in http://sources.redhat.com/ml/gdb-patches/2004-08/msg00733.html and http://sources.redhat.com/ml/gdb-patches/2004-08/msg00781.html) which I need to fix. In addition, I need to submit a generalisation of the existing STEP_SKIPS_IN_DELAY mechanism. -- Orjan Friberg Axis Communications