[Numpy-discussion] float96 on windows32 is float64?
Thu Mar 15 23:33:49 CDT 2012
I just happened to have an xp64 VM running:
My version of numpy (1.6.1) does not have float128 (see more below what I
get in ipython session).
If you need to test something else please let me know.
Enthought Python Distribution -- www.enthought.com
Python 2.7.2 |EPD 7.2-2 (64-bit)| (default, Jul 3 2011, 15:34:33) [MSC
4 bit (AMD64)]
Type "copyright", "credits" or "license" for more information.
IPython 0.12 -- An enhanced Interactive Python.
? -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help -> Python's own help system.
object? -> Details about 'object', use 'object??' for extra details.
Welcome to pylab, a matplotlib-based Python environment [backend: WXAgg].
For more information, type 'help(pylab)'.
In : import numpy as np
In : np.__version__
In : np.flo
np.float np.float32 np.float_ np.floor
np.float16 np.float64 np.floating np.floor_divide
In : np.flo
On Thu, Mar 15, 2012 at 11:25 PM, Matthew Brett <firstname.lastname@example.org>wrote:
> On Thu, Mar 15, 2012 at 9:17 PM, David Cournapeau <email@example.com>
> > On Thu, Mar 15, 2012 at 11:10 PM, Matthew Brett <firstname.lastname@example.org
> > wrote:
> >> Hi,
> >> Am I right in thinking that float96 on windows 32 bit is a float64
> >> padded to 96 bits?
> > Yes
> >> If so, is it useful?
> > Yes: this is what allows you to use dtype to parse complex binary files
> > directly in numpy without having to care so much about those details. And
> > that's how it is defined on windows in any case (C standard only forces
> > to have sizeof(long double) >= sizeof(double)).
> I propose then to rename this one to float64_96 .
> The nexp value in finfo(np.float96) is incorrect I believe, I'll make
> a ticket for it.
> >> Has anyone got a windows64
> >> box to check float128 ?
> > Too lazy to check on my vm, but I am pretty sure it is 16 bytes on
> > 64.
> Should you have time to do that, could you confirm it's also a padded
> float64 and that nexp is still (incorrectly) 15? That would be a
> great help,
> NumPy-Discussion mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion