Re: floating point library problems ...

[Greg Shubin <gshubin at sonic dot net>]

I saw this in basetype.h for ARM. At first I thougth it might be an error. THis
could cause some serious confusion. It's hard enough to decipher little-endian in
a memory dump, but big-little-endian is just too strange. Is it a standard
convention in the ARM world?

// Characterize the architecture

#ifdef __ARMEB__
# define CYG_BYTEORDER           CYG_MSBFIRST    // Big endian
#else
# define CYG_BYTEORDER           CYG_LSBFIRST    // Little endian
#endif
#define CYG_DOUBLE_BYTEORDER    CYG_MSBFIRST    // Big? endian


Luke Diamand wrote:

> Could you have some kind of problem with the endianness of doubles? See
> if you get the same problem with floats and work from there.
>
> At least on ARM, gcc assumes doubles are big-endian (the words are in
> the opposite order to the one you would expect, but within a word they
> are little endian). These leads to some weird results for the unwary...
>
> Luke Diamand
>
> Ken DESMET wrote:
> >
> > Hi all,
> >
> > I have build a cross compiler to a m68k target with the newlib-1.8.1
> > library.
> >
> > When i compile small test programs with simple floating point functions like
> > multiplications, they do work fine. More complex floating point functions
> > like sqrt() and sin() do not seem to function. They simply hang/never return
> > ...
> >
> > Any suggestions what could be the cause of this problem ?
> >
> > Greetings,
> >
> > Ken
>
> --
> Virata http://www.virata.com
> Cambridge
> Tel: +44 1223 566919      Fax: +44 1223 566915
>
> ------
> Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com