From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cagney To: Andrew Cagney Cc: Mark Kettenis , gdb-patches@sources.redhat.com Subject: Re: [rfc/rfa(DavidT?)] Move DOUBLEST to doublest.{h,c} Date: Mon, 30 Jul 2001 21:50:00 -0000 Message-id: <3B6638DE.8090803@cygnus.com> References: <3B5305B5.4070207@cygnus.com> <3B64653B.90607@cygnus.com> <3B65707C.10003@cygnus.com> <200107302128.f6ULSI508576@delius.kettenis.local> <3B65E10B.9000706@cygnus.com> X-SW-Source: 2001-07/msg00743.html > Headers such as tm-m88k.h contain macros that refer to functions such as store_floating(). I moved those functions to doublest.h. > > I see, but how about the i386/xm-*.h files? I'm asking since I'm > thinking about replacing most of them with a single xm-i386.h with the > following contents: > > > I was only checking for references to the functions I moved. Hmm, oops no, sorry, not quite... > /* FIXME: kettenis/2001-07-29: Get rid of HOST_BYTE_ORDER when Andrew > has erradicated it from the sources. */ > #define HOST_BYTE_ORDER LITTLE_ENDIAN > > #define HOST_FLOAT_FORMAT &floatformat_ieee_single_little > #define HOST_DOUBLE_FORMAT &floatformat_ieee_double_little > #define HOST_LONG_DOUBLE_FORMAT &floatformat_i387_ext > > > I'd include "floatformat.h". Is there an x86 system that doesn't have long double? I've a memory of someone pointing this out when I recently changed the i387 float conversion code. I was incorrectly adding a #include "doublest.h" when the file defined (not used) things like HOST_FLOAT_FORMAT. Further cross checking reveals that I also missed a few DOUBLEST references ;-/ I'll revise and repost. Andrew