[issue34585] Don't use AC_RUN_IFELSE to determine float endian

Benjamin Peterson added the comment: New changeset b3b8cb419e496629873fa7dda82a01863f58617a by Benjamin Peterson in branch 'master': run autoconf (GH-9411) https://github.com/python/cpython/commit/b3b8cb419e496629873fa7dda82a01863f58617a -- ___

[issue34585] Don't use AC_RUN_IFELSE to determine float endian

Benjamin Peterson added the comment: New changeset 2a9c3805ddedf282881ef7811a561c70b74f80b1 by Benjamin Peterson (Ross Burton) in branch 'master': closes bpo-34585: Don't do runtime test to get float byte order. (GH-9085)

[issue34585] Don't use AC_RUN_IFELSE to determine float endian

Change by Ned Deily : -- nosy: +mark.dickinson, tim.peters ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34585] Don't use AC_RUN_IFELSE to determine float endian

Change by Chih-Hsuan Yen : -- nosy: +yan12125 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34585] Don't use AC_RUN_IFELSE to determine float endian

Change by Ross Burton : -- pull_requests: +8543 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue34585] Don't use AC_RUN_IFELSE to determine float endian

New submission from Ross Burton : Currently configure.ac uses AC_RUN_IFELSE to determine the byte order of floats and doubles. This hurts when cross-compiling because a default is set, resulting in Python silently falling back to sub-optimal codepaths. A partial improvement would be to not