[Numpy-svn] [numpy/numpy] a61193: ENH: hard-code finfo parameters for known types (#...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/numpy/numpy
  Commit: a611932bbcb132f82472a1f222a31e120fb6dc86
      https://github.com/numpy/numpy/commit/a611932bbcb132f82472a1f222a31e120fb6dc86
  Author: Matthew Brett <matthew.brett at gmail.com>
  Date:   2017-02-03 (Fri, 03 Feb 2017)

  Changed paths:
    M doc/release/1.13.0-notes.rst
    M numpy/core/getlimits.py
    M numpy/core/tests/test_getlimits.py

  Log Message:
  -----------
  ENH: hard-code finfo parameters for known types (#8504)

* ENH: hard-code finfo parameters for known types

Hard-code the MachAr parameters for float64, float32, 80-bit extended
precision, to save time, and provide skeleton for more difficult types
such as the double double on PPC; see
https://github.com/numpy/numpy/issues/2669

* ENH: add PPC long double finfo

Add parameters for PPC long double, fixing long-standing bug for finfo
on PPC.

* BF: use Python floats for float64 finfo

For some reason (garrgh) np.exp2 with float64 gives a different answer on
Windows than it does on other platforms; use Python floating point
calculations instead, which do appear to be consistent.

* DOC: add release notes for finfo fixes

Add release note describing fixes for PPC long double ``finfo``.

* RF: try using byte string to identify floats

>From suggestion by Chuck, and
https//perl5.git.perl.org/perl.git/blob/3118d7d684b56cbeb702af874f4326683c45f045:/Configure

* TST: add tests for reasonable finfo parameters

Check that finfo returns somewhat reasonable parameters for all floating
point types.

* RF: add warning for not-recognized float type

Warn if we don't have a signature for the float type.

* NF: add IEEE float128 type signature

Still needs test on platform with IEEE float128, to check MachAr-like
parameters are correct.