https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110077
--- Comment #16 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <r...@gcc.gnu.org>: https://gcc.gnu.org/g:0867d30a68de68f4c809757348447bef94ef1491 commit r14-2661-g0867d30a68de68f4c809757348447bef94ef1491 Author: Jonathan Wakely <jwak...@redhat.com> Date: Wed Jul 19 21:15:17 2023 +0100 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.
