Re: [Numpy-discussion] [Numpy] quadruple precision

2012-03-02 Thread Pierre Haessig
Le 02/03/2012 14:39, Nathaniel Smith a écrit : > If/when someone adds __float128 support to numpy we should really just > call it float128 I agree! Other types could become "float80_128" and "float80_96", as mentioned about a week ago by Matthew. -- Pierre signature.asc Description: OpenPGP d

Re: [Numpy-discussion] [Numpy] quadruple precision

2012-03-02 Thread Nathaniel Smith
On Mar 2, 2012 10:48 AM, "Paweł Biernat" wrote: > The portability is broken for numpy.float128 anyway (as I understand, > it behaves in different ways on different architectures), so adding a > new type (call it, say, quad128) that properly supports binary128 > shouldn't be a drawback. Later on, w

Re: [Numpy-discussion] [Numpy] quadruple precision

2012-03-02 Thread Paweł Biernat
Charles R Harris gmail.com> writes: > > > The quad precision library has been there for a while, and quad precision is also supported by the Intel compiler. I don't know about MSVC. Intel has been working on adding quad precision to their hardware for several years and there is an IEEE spec

Re: [Numpy-discussion] [Numpy] quadruple precision

2012-02-29 Thread Charles R Harris
On Wed, Feb 29, 2012 at 1:09 PM, Francesc Alted wrote: > On Feb 29, 2012, at 11:52 AM, Pierre Haessig wrote: > > > Hi, > > > > Le 29/02/2012 16:22, Paweł Biernat a écrit : > >> Is there any way to interact with Fortran's real(16) (supported by gcc > >> and Intel's ifort) data type from numpy? By r

Re: [Numpy-discussion] [Numpy] quadruple precision

2012-02-29 Thread Paweł Biernat
Pierre Haessig crans.org> writes: > > Hi, > > Le 29/02/2012 16:22, Paweł Biernat a écrit : > > Is there any way to interact with Fortran's real(16) (supported by gcc > > and Intel's ifort) data type from numpy? By real(16) I mean the > > binary128 type as in IEEE 754. (In C this data type is expe

Re: [Numpy-discussion] [Numpy] quadruple precision

2012-02-29 Thread Francesc Alted
On Feb 29, 2012, at 11:52 AM, Pierre Haessig wrote: > Hi, > > Le 29/02/2012 16:22, Paweł Biernat a écrit : >> Is there any way to interact with Fortran's real(16) (supported by gcc >> and Intel's ifort) data type from numpy? By real(16) I mean the >> binary128 type as in IEEE 754. (In C this data

Re: [Numpy-discussion] [Numpy] quadruple precision

2012-02-29 Thread Pierre Haessig
Hi, Le 29/02/2012 16:22, Paweł Biernat a écrit : > Is there any way to interact with Fortran's real(16) (supported by gcc > and Intel's ifort) data type from numpy? By real(16) I mean the > binary128 type as in IEEE 754. (In C this data type is experimentally > supported as __float128 (gcc) and _Q

Re: [Numpy-discussion] [Numpy] quadruple precision

2012-02-29 Thread David Cournapeau
On Wed, Feb 29, 2012 at 10:22 AM, Paweł Biernat wrote: > I am completely new to Numpy and I know only the basics of Python, to > this point I was using Fortran 03/08 to write numerical code. However, > I am starting a new large project of mine and I am looking forward to > using Python to call som

Re: [Numpy-discussion] [Numpy] quadruple precision

2012-02-29 Thread Matthew Brett
Hi, On Wed, Feb 29, 2012 at 12:13 PM, Jonathan Rocher wrote: > Thanks to your question, I discovered that there is a float128 dtype in > numpy > > In[5]: np.__version__ > Out[5]: '1.6.1' > > In[6]: np.float128? > Type:   type > Base Class: > String Form: > Namespace:  Interactive > File: > /

Re: [Numpy-discussion] [Numpy] quadruple precision

2012-02-29 Thread Jonathan Rocher
Thanks to your question, I discovered that there is a float128 dtype in numpy In[5]: np.__version__ Out[5]: '1.6.1' In[6]: np.float128? Type: type Base Class: String Form: Namespace: Interactive File: /Library/Frameworks/Python.framework/Versions/7.2/lib/python2.7/site-packages/numpy/__in

[Numpy-discussion] [Numpy] quadruple precision

2012-02-29 Thread Paweł Biernat
I am completely new to Numpy and I know only the basics of Python, to this point I was using Fortran 03/08 to write numerical code. However, I am starting a new large project of mine and I am looking forward to using Python to call some low level Fortran code responsible for most of the intensive n