https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98389
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Last reconfirmed| |2020-12-19
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Andreas Schwab from comment #1)
> The list just needs to be updated.
No, those have version GLIBCXX_3.4.29 which is the current version, so new
symbols are allowed there.
The problem is this check in testsuite/util/testsuite_abi.cc:
// Check that long double compatibility symbols demangled as
// __float128 and regular __float128 symbols are put into some _LDBL_
// or _FLOAT128 version name.
if (added && test.demangled_name.find("__float128") != std::string::npos
&& test.demangled_name.find("std::__cxx11::") != 0)
I need to think about what the right fix is here (to change the test, or the
symbol versions of those symbols). That's unlikely to happen until January.
