From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3997 invoked by alias); 4 Feb 2002 14:43: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 3894 invoked from network); 4 Feb 2002 14:43:31 -0000 Received: from unknown (HELO fw-cam.cambridge.arm.com) (193.131.176.3) by sources.redhat.com with SMTP; 4 Feb 2002 14:43:31 -0000 Received: by fw-cam.cambridge.arm.com; id OAA11543; Mon, 4 Feb 2002 14:43:27 GMT Received: from unknown(172.16.1.2) by fw-cam.cambridge.arm.com via smap (V5.5) id xma010610; Mon, 4 Feb 02 14:42:36 GMT Received: from cam-mail2.cambridge.arm.com (localhost [127.0.0.1]) by cam-admin0.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id OAA14512 for ; Mon, 4 Feb 2002 14:42:35 GMT Received: from sun18.cambridge.arm.com (sun18.cambridge.arm.com [172.16.2.18]) by cam-mail2.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id OAA29219; Mon, 4 Feb 2002 14:42:34 GMT Message-Id: <200202041442.OAA29219@cam-mail2.cambridge.arm.com> X-Mailer: exmh version 2.0.2 2/24/98 To: gdb@sources.redhat.com cc: Richard.Earnshaw@arm.com Reply-To: Richard.Earnshaw@arm.com Organization: ARM Ltd. X-Telephone: +44 1223 400569 (direct+voicemail), +44 1223 400400 (switchbd) X-Fax: +44 1223 400410 X-Address: ARM Ltd., 110 Fulbourn Road, Cherry Hinton, Cambridge CB1 9NJ. X-Url: http://www.arm.com/ Subject: Multi-arching FLOAT_INFO Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Feb 2002 06:43:00 -0000 From: Richard Earnshaw X-SW-Source: 2002-02/txt/msg00076.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. R.