diff options
author | Jonathan Wakely <jwakely@redhat.com> | 2022-02-10 14:06:27 +0000 |
---|---|---|
committer | Jonathan Wakely <jwakely@redhat.com> | 2022-02-14 12:34:21 +0000 |
commit | 813415650235b8ca42fe1afb3fcb0430e8628d30 (patch) | |
tree | 3bb3be50de2ac68600f46007390232618c0cbb67 /gcc | |
parent | f320197c8b495324dc6997a99d53e7f45ecf5840 (diff) | |
download | gcc-813415650235b8ca42fe1afb3fcb0430e8628d30.zip gcc-813415650235b8ca42fe1afb3fcb0430e8628d30.tar.gz gcc-813415650235b8ca42fe1afb3fcb0430e8628d30.tar.bz2 |
libstdc++: Fix std::to_chars for IEEE128 long double
The preprocessor check for _GLIBCXX_USE_FLOAT128 is the wrong condition,
because when the compiler is built with --with-long-double-format=ieee
configure determines that __float128 is the same as long double, and so
should not be used. But we do want the std::to_chars overloads for
__float128 in that case, because the floating_to_chars.cc file is built
with -mabi=ibmlongdouble and so the __float128 overloads are actually
the 'long double' ones for -mabi=ieeelongdouble code.
This fixes missing definitions of the __float128 overloads of
std::to_chars for --with-long-double-format=ieee builds. Without this,
there are symbols present in the --with-long-double-abi=ibm build which
are missing from the --with-long-double-abi=ieee build.
libstdc++-v3/ChangeLog:
* src/c++17/floating_to_chars.cc (FLOAT128_TO_CHARS): Depend on
LONG_DOUBLE_ALT128_COMPAT instead of USE_FLOAT128.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions