This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Multi-arching FLOAT_INFO
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: gdb at sources dot redhat dot com
- Cc: Richard dot Earnshaw at arm dot com
- Date: Mon, 04 Feb 2002 14:42:34 +0000
- Subject: Multi-arching FLOAT_INFO
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
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.