From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24888 invoked by alias); 2 Dec 2001 06:36:52 -0000 Mailing-List: contact gdb-patches-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 24862 invoked from network); 2 Dec 2001 06:36:46 -0000 Received: from unknown (HELO localhost.cygnus.com) (24.114.42.213) by hostedprojects.ges.redhat.com with SMTP; 2 Dec 2001 06:36:46 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id CDBDE3DF9; Sun, 2 Dec 2001 01:36:40 -0500 (EST) Message-ID: <3C09CBF8.7020708@cygnus.com> Date: Sat, 01 Dec 2001 22:36:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.3) Gecko/20011020 X-Accept-Language: en-us MIME-Version: 1.0 To: Jason Molenda Cc: gdb-patches@sources.redhat.com Subject: Re: [patch] Zap a29k ultra native stuff References: <20011201212654.A47602@molenda.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2001-12/txt/msg00013.txt.bz2 >> The a29k is very much on notice (obsolete announcement sent out). > Does this mean you're looking at dropping the utils/amd-udi directory > as well? This is some code to talk to a ROM monitor that was used > on 29k boards long ago, it's a code drop of AMD's own support code > slightly munged to work in our build setup. Mostly, though, it's > 1.4MB of wasted disk space on every gdb checkout these days. Yep (delete a29k?)! The below went out problably 1s after 5.1 was released. Hmm, forgot to cc gdb@, I'll forward the original post. I'm playing with a draft patch in my local sandpit. The number of remote-*.c targets that are deleted is suprising. This must have been a popular target back in its time. enjoy, Andrew > [Reply-to: GDB Discussion < gdb AT sources DOT redhat DOT com > ] > > Hello, > > As part of GDB 5.2, the a29k target > > a29k-* (a29k-aout, a29k-coff, ...) > > has been identified as a candidate for obsolescence. This target: > > o depends on the the macro HOST_BYTE_ORDER > which is being deleted from GDB. > > o does not build multi-arch. > > o has no active maintainer > > ``Configurations that have been declared obsolete in this release have > been commented out. Unless there is activity to revive these > configurations, the next release of GDB will have their sources > permanently REMOVED.'' > > If you have any comments or questions on this, please send them to the GDB Discussion group. > > Andrew > > Andrew Cagney > Acting Head GDB Maintainer >