Boost logo

Boost :

From: Boris Gubenko (Boris.Gubenko_at_[hidden])
Date: 2006-10-17 10:24:27


Boris Gubenko wrote:
> I'm checking with the OS folks and will report back here,
> for both HP-UX/ia64 and Tru64 Alpha.

And the answer is:

> You are correct that both platforms are capable of executing in
> either endianness. However, the operating systems operate in only
> one.
> HP-UX is *always* big endian
> Tru64 is *always* little endian
> [...]
> Summary:
> A compile time check is adequate.
>

So, with current <endian.hpp>, I think, that we are all set for
these platforms.

Thanks,
  Boris

----- Original Message -----
From: "Boris Gubenko" <Boris.Gubenko_at_[hidden]>
To: <boost_at_[hidden]>
Cc: "Boris Gubenko" <Boris.Gubenko_at_[hidden]>
Sent: Tuesday, October 17, 2006 9:12 AM
Subject: Re: [boost] Optimized portable isnan, isfinite, fpclassify etc

>> Now endian.hpp defines BOOST_BIG_ENDIAN on HP-UX.
>> This was suggested by Boris Gubenko.
>>
>> If you are right John, then this seems to be incorrect.
>> Shouldn't endian.hpp then define something like
>> BOOST_UNKNOWN_ENDIAN on HP-UX?
>>
>> Boris, do you have any comments on this?
>
> I'm checking with the OS folks and will report back here,
> for both HP-UX/ia64 and Tru64 Alpha.
>
> Thanks,
> Boris
>
> ----- Original Message -----
> From: "Johan Råde" <rade_at_[hidden]>
> To: <boost_at_[hidden]>
> Sent: Tuesday, October 17, 2006 9:00 AM
> Subject: Re: [boost] Optimized portable isnan, isfinite, fpclassify etc
>
>
>> John Maddock wrote:
>>> I'm not completely certain, but I believe HP-UX falls into this
>>> category:
>>> the idea is that you can pass binary data from one platform to another,
>>> and
>>> just switch the endianness bit to access it natively (think distributed
>>> applications).
>>
>> Now endian.hpp defines BOOST_BIG_ENDIAN on HP-UX.
>> This was suggested by Boris Gubenko.
>>
>> If you are right John, then this seems to be incorrect.
>> Shouldn't endian.hpp then define something like BOOST_UNKNOWN_ENDIAN on
>> HP-UX?
>>
>> Boris, do you have any comments on this?
>>
>> Then my fpclassify could use a fast implementation when BOOST_BIG_ENDIAN
>> or BOOST_LITTLE_ENDIAN is defined and a slower implementation when
>> BOOST_UNKNOWN_ENDIAN is defined.
>>
>> --Johan
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Unsubscribe & other changes:
>> http://lists.boost.org/mailman/listinfo.cgi/boost
>>
>>
>


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk