[Numpy-discussion] Solaris Sparc build broken
Charles R Harris
Wed Nov 4 13:47:24 CST 2009
On Wed, Nov 4, 2009 at 12:38 PM, Charles R Harris <firstname.lastname@example.org
> On Wed, Nov 4, 2009 at 12:35 PM, Charles R Harris <
> email@example.com> wrote:
>> On Wed, Nov 4, 2009 at 12:11 PM, David Cournapeau <firstname.lastname@example.org>wrote:
>>> On Thu, Nov 5, 2009 at 2:15 AM, Michael Droettboom <email@example.com>
>>> > I'm getting the following from r7603 on Solaris Sparc -- somehow
>>> > to not having a long double version of next after available. I realise
>>> > not everyone has access to (or is dependent on) this platform, so I'm
>>> > willing to help in whatever way I can, I'm just not sure I understand
>>> > the change yet.
>>> The only way to implement nextafter that I know of requires to know
>>> the exact representation of the floating point number, and long double
>>> is unfortunately platform dependent.
>>> What is the long double format on solaris sparc ? (big endian I
>>> suppose, but how many bits for the mantissa and exponent ? Does it
>>> follow IEER754 ?)
>> Long double on SPARC is quad precision, which I believe *is* in one of the
>> ieee specs. In any case, it has a lot more precision than the extended
>> precision found in Intel derived architectures. Hmm, I wonder what ia64
> HP9000 also has quad precision:
And it looks like extended precision has disappeared from the latest version
or the ieee_754-2008 <http://wapedia.mobi/en/IEEE_754-2008>standard, being
replaced by quad precision. I know Intel is also working on quad precision
FPU's, so I think that is where things are heading.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion