diff options
| author | Ross Burton <ross@burtonini.com> | 2018-09-19 06:25:48 (GMT) |
|---|---|---|
| committer | Benjamin Peterson <benjamin@python.org> | 2018-09-19 06:25:48 (GMT) |
| commit | 2a9c3805ddedf282881ef7811a561c70b74f80b1 (patch) | |
| tree | f50deac3aa512a6932c1c459a0d77b3d6a101580 /Misc/NEWS.d | |
| parent | 471503954a91d86cf04228c38134108c67a263b0 (diff) | |
| download | cpython-2a9c3805ddedf282881ef7811a561c70b74f80b1.zip cpython-2a9c3805ddedf282881ef7811a561c70b74f80b1.tar.gz cpython-2a9c3805ddedf282881ef7811a561c70b74f80b1.tar.bz2 | |
closes bpo-34585: Don't do runtime test to get float byte order. (GH-9085)
Currently configure.ac uses AC_RUN_IFELSE to determine the byte order of doubles, but this silently fails under cross compilation and Python doesn't do floats properly.
Instead, steal a macro from autoconf-archive which compiles code using magic doubles (which encode to ASCII) and grep for the representation in the binary.
RFC because this doesn't yet handle the weird ancient ARMv4 OABI 'mixed-endian' encoding properly. This encoding is ancient and I don't believe the union of "Python 3.8 users" and "OABI users" has anything in. Should the support for this just be dropped too? Alternatively, someone will need to find an OABI toolchain to verify the encoding of the magic double.
Diffstat (limited to 'Misc/NEWS.d')
| -rw-r--r-- | Misc/NEWS.d/next/Build/2018-09-18-16-28-31.bpo-34585.CGMu0h.rst | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/Misc/NEWS.d/next/Build/2018-09-18-16-28-31.bpo-34585.CGMu0h.rst b/Misc/NEWS.d/next/Build/2018-09-18-16-28-31.bpo-34585.CGMu0h.rst new file mode 100644 index 0000000..01318e6 --- /dev/null +++ b/Misc/NEWS.d/next/Build/2018-09-18-16-28-31.bpo-34585.CGMu0h.rst @@ -0,0 +1,3 @@ +Check for floating-point byte order in configure.ac using compilation tests +instead of executing code, so that these checks work in cross-compiled +builds. |