From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13086 invoked by alias); 18 Jun 2002 13:52:33 -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 13034 invoked from network); 18 Jun 2002 13:52:30 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 18 Jun 2002 13:52:30 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id DCD043D32; Tue, 18 Jun 2002 09:52:30 -0400 (EDT) Message-ID: <3D0F3B1E.5020308@cygnus.com> Date: Tue, 18 Jun 2002 06:52:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020613 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Frank Ch. Eigler" Cc: gdb@sources.redhat.com Subject: Re: Obsolete GDB's m32r support References: <3D0E7DF7.90409@cygnus.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-06/txt/msg00133.txt.bz2 > cagney wrote: > > >> [...] This target does not use GDB's multi-arch framework and all >> such targets are either being obsoleted or multi-arched. [...] > > > Can you summarize the technical reasons for this dichotomy of > outcomes? In what way does the presence of old targets pose a > technical challenge to more modern multiarch'd ones? In other words, > what technical reasons exist to not allow old targets to stick around > as they are? The rationale for this move has been discussed on a number of occasions in the past, can I recommend a quick search through the e-mail archives and a review of that previous debate. Andrew