From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22057 invoked by alias); 27 May 2002 05:43:08 -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 22043 invoked from network); 27 May 2002 05:43:06 -0000 Received: from unknown (HELO mail-out1.apple.com) (17.254.0.52) by sources.redhat.com with SMTP; 27 May 2002 05:43:06 -0000 Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.11.3/8.11.3) with ESMTP id g4R5h6t07123; Sun, 26 May 2002 22:43:06 -0700 (PDT) Received: from scv1.apple.com (scv1.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Sun, 26 May 2002 22:42:27 -0700 Received: from apple.com (vpn-gh-1066.apple.com [17.254.140.41]) by scv1.apple.com (8.11.3/8.11.3) with ESMTP id g4R5gx908690; Sun, 26 May 2002 22:42:59 -0700 (PDT) Message-ID: <3CF1C761.28A0AC96@apple.com> Date: Sun, 26 May 2002 22:43:00 -0000 From: Stan Shebs Organization: Apple Computer, Inc. X-Accept-Language: en MIME-Version: 1.0 To: Nathanael Nerode CC: gcc@gcc.gnu.org, binutils@sources.redhat.com, gdb@sources.redhat.com Subject: Re: obselete configurations & the top level References: <20020527052330.GA25946@doctormoo.dyndns.org> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-SW-Source: 2002-05/txt/msg00286.txt.bz2 Nathanael Nerode wrote: > > This is a query. A bunch of configurations have been obseleted and > removed from GCC recently. These have all, I believe, been obseleted > and removed from GDB already. > > There is special-case code for many of these configurations in > configure.in. I would like to get rid of it. > > What else do I need to check before I get rid of these cases? Are any > of them possibly still supported by binutils? While it's certainly conceivable that some targets should be binutils-only (z8k is almost in that category for instance), these are going to be unusual cases and there should be lots of details about them in the top level files somewhere. The onus should be on the maintainers of any such config to speak up and to document the situation thoroughly, and in the absence of any such info, you should feel free to propose such cleanups. (And thanks in advance for doing it!) Stan