Describe WebAssembly's C/C++ ABI floating point types.

The rationale for making C/C++ long double something other than 64-bit is:
 - there are use cases for quad-precision floating point types, and
   "long double" is a friendlier way to satisfy those use cases than
   extensions like "__float128" since "long double" has the benefit of libm
   and printf API support.
 - long double is a lost cause in terms of portable functionality anyway.
   64-bit, 80-bit, and 128-bit long double types are in use in popular
   platforms, so people who want portable results aren't using it.
 - it's also a lost cause in terms of portable performance, as it's
   already significantly slower than double on several widely popular
   platforms, so people who want portable performance already have
   motivation to avoid it.

The rationale for picking quad-precision over double-double is that even
though double-double can be significantly faster, it has surprising
numeric properties which make it undesirable to impose on unsuspecting
code.

0 files changed, 0 insertions, 0 deletions