https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110077
--- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Jonathan Wakely from comment #10) > (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. Actually that's not true, we always define it in the library but for old glibc we *don't* declare it in the header. So to make Solaris x86 consistent we'd just want to fix up the symbol version.
