https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110077
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Jonathan Wakely from comment #9) > One solution would be to just add the declaration to the header, and adjust > the exports so this new symbol is exported at GLIBCXX_3.4.32 not > GLIBCXX_3.4.31 N.B. this is what we do for glibc-based linux targets. The symbol is present in the library even when glibc doesn't provide strtof128. This means that we don't have a different set of exported symbols when built on old or new glibc. If Solaris is ever going to get support for strtof128 and other _Float128 support then that is probably what we should do here as well.
