From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31350 invoked by alias); 4 Feb 2002 16:33:44 -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 31279 invoked from network); 4 Feb 2002 16:33:41 -0000 Received: from unknown (HELO localhost.redhat.com) (24.114.26.18) by sources.redhat.com with SMTP; 4 Feb 2002 16:33:41 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id DADBF3E55; Mon, 4 Feb 2002 11:33:40 -0500 (EST) Message-ID: <3C5EB7E4.9080700@cygnus.com> Date: Mon, 04 Feb 2002 08:33: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: Richard.Earnshaw@arm.com Cc: gdb@sources.redhat.com Subject: Re: Multi-arching FLOAT_INFO References: <200202041442.OAA29219@cam-mail2.cambridge.arm.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-02/txt/msg00080.txt.bz2 > So it turns out that multi-arching FLOAT_INFO may not be completely > trivial either. Only two ports really make use of this: ARM and i386. > The ARM code is straight-forward, but the code on the i386 is largely > disabled. Indeed, the largest problem is i386b-nat.c which contains a > large chunk of code that is surrounded in "#ifdef FLOAT_INFO". This file > seems to only be used on BSD4.4 systems (FreeBSD, NetBSD and OpenBSD all > seem to use their own nat files -- I'm not sure what BSDi uses). > > Since adding FLOAT_INFO to gdbarch will mean that it is now > unconditionally defined the question is - how to handle this chunk of > code. I've no idea (and no way of testing) whether it will even compile > cleanly. > > Does anyone even use a system that relies on this file now? > > Suggestions welcome. Have a look at REGISTER_NAME() vs REGISTER_NAMES and legacy_register_name. There is no reason for you fixing anything other than the arm. As for FLOAT_INFO, file a bug report indicating that it is deprecated. I'll also ARI it. Andrew