mirror of https://github.com/python/cpython
gh-89640: Hardcode WASM float word ordering as little endian (#126387)
This commit is contained in:
parent
9b7294c3a5
commit
532fc08102
|
@ -0,0 +1 @@
|
|||
Hard-code float word ordering as little endian on WASM.
|
|
@ -24227,41 +24227,34 @@ printf "%s\n" "$ax_cv_c_float_words_bigendian" >&6; }
|
|||
case $ax_cv_c_float_words_bigendian in
|
||||
yes)
|
||||
|
||||
printf "%s\n" "#define FLOAT_WORDS_BIGENDIAN 1" >>confdefs.h
|
||||
printf "%s\n" "#define DOUBLE_IS_BIG_ENDIAN_IEEE754 1" >>confdefs.h
|
||||
;;
|
||||
no)
|
||||
;;
|
||||
|
||||
printf "%s\n" "#define DOUBLE_IS_LITTLE_ENDIAN_IEEE754 1" >>confdefs.h
|
||||
;;
|
||||
*)
|
||||
as_fn_error $? "
|
||||
case $host_cpu in #(
|
||||
*arm*) :
|
||||
# Some ARM platforms use a mixed-endian representation for
|
||||
# doubles. While Python doesn't currently have full support
|
||||
# for these platforms (see e.g., issue 1762561), we can at
|
||||
# least make sure that float <-> string conversions work.
|
||||
# FLOAT_WORDS_BIGENDIAN doesn't actually detect this case,
|
||||
# but if it's not big or little, then it must be this?
|
||||
|
||||
Unknown float word ordering. You need to manually preset
|
||||
ax_cv_c_float_words_bigendian=no (or yes) according to your system.
|
||||
printf "%s\n" "#define DOUBLE_IS_ARM_MIXED_ENDIAN_IEEE754 1" >>confdefs.h
|
||||
;; #(
|
||||
wasm*) :
|
||||
|
||||
" "$LINENO" 5 ;;
|
||||
printf "%s\n" "#define DOUBLE_IS_LITTLE_ENDIAN_IEEE754 1" >>confdefs.h
|
||||
;; #(
|
||||
*) :
|
||||
;;
|
||||
esac ;;
|
||||
esac
|
||||
|
||||
|
||||
if test "$ax_cv_c_float_words_bigendian" = "yes"
|
||||
then
|
||||
|
||||
printf "%s\n" "#define DOUBLE_IS_BIG_ENDIAN_IEEE754 1" >>confdefs.h
|
||||
|
||||
elif test "$ax_cv_c_float_words_bigendian" = "no"
|
||||
then
|
||||
|
||||
printf "%s\n" "#define DOUBLE_IS_LITTLE_ENDIAN_IEEE754 1" >>confdefs.h
|
||||
|
||||
else
|
||||
# Some ARM platforms use a mixed-endian representation for doubles.
|
||||
# While Python doesn't currently have full support for these platforms
|
||||
# (see e.g., issue 1762561), we can at least make sure that float <-> string
|
||||
# conversions work.
|
||||
# FLOAT_WORDS_BIGENDIAN doesn't actually detect this case, but if it's not big
|
||||
# or little, then it must be this?
|
||||
|
||||
printf "%s\n" "#define DOUBLE_IS_ARM_MIXED_ENDIAN_IEEE754 1" >>confdefs.h
|
||||
|
||||
fi
|
||||
|
||||
# The short float repr introduced in Python 3.1 requires the
|
||||
# correctly-rounded string <-> double conversion functions from
|
||||
|
|
42
configure.ac
42
configure.ac
|
@ -5946,28 +5946,26 @@ AS_VAR_IF([ac_cv_gcc_asm_for_x64], [yes], [
|
|||
# * Check for various properties of floating point *
|
||||
# **************************************************
|
||||
|
||||
AX_C_FLOAT_WORDS_BIGENDIAN
|
||||
if test "$ax_cv_c_float_words_bigendian" = "yes"
|
||||
then
|
||||
AC_DEFINE([DOUBLE_IS_BIG_ENDIAN_IEEE754], [1],
|
||||
[Define if C doubles are 64-bit IEEE 754 binary format, stored
|
||||
with the most significant byte first])
|
||||
elif test "$ax_cv_c_float_words_bigendian" = "no"
|
||||
then
|
||||
AC_DEFINE([DOUBLE_IS_LITTLE_ENDIAN_IEEE754], [1],
|
||||
[Define if C doubles are 64-bit IEEE 754 binary format, stored
|
||||
with the least significant byte first])
|
||||
else
|
||||
# Some ARM platforms use a mixed-endian representation for doubles.
|
||||
# While Python doesn't currently have full support for these platforms
|
||||
# (see e.g., issue 1762561), we can at least make sure that float <-> string
|
||||
# conversions work.
|
||||
# FLOAT_WORDS_BIGENDIAN doesn't actually detect this case, but if it's not big
|
||||
# or little, then it must be this?
|
||||
AC_DEFINE([DOUBLE_IS_ARM_MIXED_ENDIAN_IEEE754], [1],
|
||||
[Define if C doubles are 64-bit IEEE 754 binary format, stored
|
||||
in ARM mixed-endian order (byte order 45670123)])
|
||||
fi
|
||||
AX_C_FLOAT_WORDS_BIGENDIAN(
|
||||
[AC_DEFINE([DOUBLE_IS_BIG_ENDIAN_IEEE754], [1],
|
||||
[Define if C doubles are 64-bit IEEE 754 binary format,
|
||||
stored with the most significant byte first])],
|
||||
[AC_DEFINE([DOUBLE_IS_LITTLE_ENDIAN_IEEE754], [1],
|
||||
[Define if C doubles are 64-bit IEEE 754 binary format,
|
||||
stored with the least significant byte first])],
|
||||
[AS_CASE([$host_cpu],
|
||||
[*arm*], [# Some ARM platforms use a mixed-endian representation for
|
||||
# doubles. While Python doesn't currently have full support
|
||||
# for these platforms (see e.g., issue 1762561), we can at
|
||||
# least make sure that float <-> string conversions work.
|
||||
# FLOAT_WORDS_BIGENDIAN doesn't actually detect this case,
|
||||
# but if it's not big or little, then it must be this?
|
||||
AC_DEFINE([DOUBLE_IS_ARM_MIXED_ENDIAN_IEEE754], [1],
|
||||
[Define if C doubles are 64-bit IEEE 754 binary format,
|
||||
stored in ARM mixed-endian order (byte order 45670123)])],
|
||||
[wasm*], [AC_DEFINE([DOUBLE_IS_LITTLE_ENDIAN_IEEE754], [1],
|
||||
[Define if C doubles are 64-bit IEEE 754 binary format,
|
||||
stored with the least significant byte first])])])
|
||||
|
||||
# The short float repr introduced in Python 3.1 requires the
|
||||
# correctly-rounded string <-> double conversion functions from
|
||||
|
|
|
@ -47,10 +47,6 @@
|
|||
/* Define if --enable-ipv6 is specified */
|
||||
#undef ENABLE_IPV6
|
||||
|
||||
/* Define to 1 if your system stores words within floats with the most
|
||||
significant word first */
|
||||
#undef FLOAT_WORDS_BIGENDIAN
|
||||
|
||||
/* Define if getpgrp() must be called as getpgrp(0). */
|
||||
#undef GETPGRP_HAVE_ARG
|
||||
|
||||
|
|
Loading…
Reference in New Issue