From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31787 invoked by alias); 19 Jan 2002 16:57:11 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 31755 invoked from network); 19 Jan 2002 16:57:10 -0000 Received: from unknown (HELO localhost.cygnus.com) (24.114.42.213) by sources.redhat.com with SMTP; 19 Jan 2002 16:57:10 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id 2A18F3D67; Sat, 19 Jan 2002 11:57:10 -0500 (EST) Message-ID: <3C49A566.1060508@cygnus.com> Date: Sat, 19 Jan 2002 08:57:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: [patch/rfc] Eliminate TARGET_BYTE_ORDER_SELECTABLE References: <3C490B0C.6090601@cygnus.com> <20020119094718.A1404@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-01/txt/msg00530.txt.bz2 > On Sat, Jan 19, 2002 at 12:58:36AM -0500, Andrew Cagney wrote: > >> Hello, >> >> All multi-arch targets (yep, including the i386) allow the byte order to >> be selected at run time. This means that the macro >> TARGET_BYTE_ORDER_SELECTABLE which was used by non-multi-arch targets is >> obsolete. >> >> The attached patch eliminates that macro. I've tested it on a >> multi-arch target and I don't think it breaks non-multi-arch targets. >> >> Anyway, I intend committing this in a few days. >> Andrew > > > Hmm, I don't know. Do we really want to do this? This allows, for > instance, 'set endian big' on i386. That may someday make someone > think that GDB supports such a beast, on the off chance one is ever > made. Ah, but we live in dangerous times :-) TARGET_BYTE_ORDER_SELECTABLE, TARGET_BYTE_ORDER_SELECTABLE_P and even TARGET_BYTE_ORDER_DEFAULT are all there just to prop up old pre- multi-arch targets. They are not used by a multi-arch GDB. All multi-arch architectures allow both big and little byte orders (regardless of what the spec says). This lets the user do things like: (gdb) print network_structure (gdb) set endian big (gdb) print network_structure enjoy, Andrew