diff options
| author | Jonathan Wakely <jwakely@redhat.com> | 2023-07-19 21:15:17 +0100 |
|---|---|---|
| committer | Jonathan Wakely <jwakely@redhat.com> | 2023-07-19 23:42:56 +0100 |
| commit | 0867d30a68de68f4c809757348447bef94ef1491 (patch) | |
| tree | 67d41954794db0a19652fe92abb4546f4368d87c /libgcc | |
| parent | 2d614822e9ea2a3d8800045d66e3220743753d09 (diff) | |
| download | gcc-0867d30a68de68f4c809757348447bef94ef1491.zip gcc-0867d30a68de68f4c809757348447bef94ef1491.tar.gz gcc-0867d30a68de68f4c809757348447bef94ef1491.tar.bz2 | |
libstdc++: Do not define inaccurate from_chars for _Float128 [PR110077]
I think r14-1431-g7037e7b6e4ac41 was wrong to try to define the
_Float128 overload unconditionally. Not all targets need it, so defining
the lossy fallback using long double is not useful (and caused an ABI
change on Solaris x86).
Making the definition depend on USE_STRTOF128_FOR_FROM_CHARS again
partially reverts the change for PR 109921, however that should still be
fixed because the changes to make USE_STRTOF128_FOR_FROM_CHARS depend on
USE_STRTOD_FOR_FROM_CHARS are not reverted.
libstdc++-v3/ChangeLog:
PR libstdc++/110077
* src/c++17/floating_from_chars.cc (from_chars): Only define
_Float128 overload when using __strfromf128.
Diffstat (limited to 'libgcc')
0 files changed, 0 insertions, 0 deletions