This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: real.c on unicosmk


On Wed, May 22, 2002 at 02:16:19PM +0200, Roman Lechtchinsky wrote:
> 
> I've now implemented it such that the sign, the exponent and the high
> guard are stored in separate words while the low guard occupies the lower
> 16 bits of the last 32-bit word. This seems to be the most convienient
> representation. Arithmetic seems to work ok.

Sounds good.

> However, I don't really understand the various target-specific
> representations (i.e. e24, e53 etc.). Unless I've missed something they
> are only used internally, but the actual representation depends on
> REAL_WORDS_BIG_ENDIAN which considerably complicates the code now and
> becomes a real mess with my changes. Is there any good reason for this
> dependency or can I safely remove it? Then, endian would be the only
> function which takes the endianness of the target into account.

I don't see any good reason.  The ereal_from_* functions still have to
care about endianness, but I don't think that's your problem -- you're
talking about etoeXX and eXXtoe, right?

zw


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]