From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3968 invoked by alias); 12 Dec 2004 15:16:35 -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 3599 invoked from network); 12 Dec 2004 15:16:28 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 12 Dec 2004 15:16:28 -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 iBCFGMEF008250 for ; Sun, 12 Dec 2004 10:16:27 -0500 Received: from localhost.redhat.com (vpn50-50.rdu.redhat.com [172.16.50.50]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id iBCFGHr29403; Sun, 12 Dec 2004 10:16:17 -0500 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 0690B3EF9; Sun, 12 Dec 2004 10:14:15 -0500 (EST) Message-ID: <41BC6047.1080308@gnu.org> Date: Sun, 12 Dec 2004 15:16:00 -0000 From: Andrew Cagney User-Agent: Mozilla Thunderbird 0.8 (X11/20041020) MIME-Version: 1.0 To: Peter Barada , brian.laponsey@freescale.com Cc: gdb@sources.redhat.com, Daniel Jacobwitz Subject: Re: mcore-*-* target to be deleted? References: <1101996241.4678.13.camel@blapo.sps.mot.com> <20041202142155.C2D5E9842C@baradas.org> In-Reply-To: <20041202142155.C2D5E9842C@baradas.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-12/txt/msg00083.txt.bz2 Peter Barada wrote: >>I (belatedly) noticed an announcement on the GDB web page that the mcore >>target has been declared obsolete and is going to be deleted from gdb in >>the next release. >> >>I have made some inquiries about the impact this would have on our >>customers, and although the response wasn't huge, it was definitely not >>zero. There's a small but determined population of developers who >>continue to use gdb with mcore. It also has a small but growing market >>with small firms working through distributors, as well as a new design >>group in China that prefers to use non-Microsoft tools. >> >>I don't know if one vote matters, but I vote to save the mcore. The mcore code has, unfortunatly, become very out of date. The mainline hasn't built since 6.2 was released, and with 6.3 past that broken code was dropped. This all came about because GDB's frame code was rewritten from scratch and the mcore was never updated to work with the new code. The way to revive the mcore isn't through votes, nominations, or appointments, it's through code. A developer with an assignment contributes code to current standards (most importantly does not use deprecated interfaces) then it can very easily be re-integrated (and they may quickly find themselves in a more responsible role). Any questions on how to do it welcome(1). Andrew (1) Exprerience suggests that largely starting from scratch (using the existing code as a guideline) is easier. This is because the bulk of the current file is redundant.