diff options
| author | Jérôme Pouiller <jezz@sysmic.org> | 2016-11-09 10:25:07 +0100 |
|---|---|---|
| committer | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2016-11-09 21:57:18 +0100 |
| commit | 2a6001f17aba3f405f1aa95b3d95a553761d9b03 (patch) | |
| tree | 3003a42160f59f8c8516eff40cc3698e7fc1a555 /package/gcc/gcc-initial/gcc-initial.hash | |
| parent | 0aff35482ca469288d038437e4760741043e5ccc (diff) | |
| download | buildroot-2a6001f17aba3f405f1aa95b3d95a553761d9b03.tar.gz buildroot-2a6001f17aba3f405f1aa95b3d95a553761d9b03.zip | |
python: fix double format detection
Python is not able to detect if compiler double representation is
compliant with IEE754:
checking whether C doubles are little-endian IEEE 754 binary64... no
checking whether C doubles are big-endian IEEE 754 binary64... no
checking whether C doubles are ARM mixed-endian IEEE 754 binary64... no
Accordingly 'legacy' mode isused. It is possible to check this at
runtime by check if 'sys.float_repr_style' contains 'short' or
'legacy'. Calculus correctness is not garanteed with 'legacy'.
Problem is better described here:
http://stackoverflow.com/questions/29920294/what-causes-pythons-float-repr-style-to-use-legacy
https://bugs.python.org/issue7117
However, all gcc architecture use a representation compliant with
IEE754. So, we can enable it unconditionnaly.
Signed-off-by: Jérôme Pouiller <jezz@sysmic.org>
[Thomas: adjust condition to avoid usage of qstrip, suggested by Baruch.]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'package/gcc/gcc-initial/gcc-initial.hash')
0 files changed, 0 insertions, 0 deletions
