Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* Multi-arching FLOAT_INFO
@ 2002-02-04  6:43 Richard Earnshaw
  2002-02-04  8:33 ` Andrew Cagney
  0 siblings, 1 reply; 6+ messages in thread
From: Richard Earnshaw @ 2002-02-04  6:43 UTC (permalink / raw)
  To: gdb; +Cc: Richard.Earnshaw


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.


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2002-02-05 16:52 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-02-04  6:43 Multi-arching FLOAT_INFO Richard Earnshaw
2002-02-04  8:33 ` Andrew Cagney
2002-02-05  2:34   ` Richard Earnshaw
2002-02-05  7:41     ` Andrew Cagney
2002-02-05  7:57       ` Richard Earnshaw
2002-02-05  8:52         ` Andrew Cagney

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox