public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/98389] [11 regression] libstdc++-abi/abi_check fails after r11-6249 on powerpc64 big endian
Date: Sat, 19 Dec 2020 13:58:44 +0000 [thread overview]
Message-ID: <bug-98389-4-Zn24RznBX1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98389-4@http.gcc.gnu.org/bugzilla/>
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.
next prev parent reply other threads:[~2020-12-19 13:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 7:09 [Bug libstdc++/98389] New: " seurer at gcc dot gnu.org
2020-12-19 9:01 ` [Bug libstdc++/98389] " schwab@linux-m68k.org
2020-12-19 13:58 ` redi at gcc dot gnu.org [this message]
2021-01-05 9:11 ` rguenth at gcc dot gnu.org
2021-02-19 14:30 ` redi at gcc dot gnu.org
2021-02-19 15:18 ` redi at gcc dot gnu.org
2021-02-19 15:37 ` jakub at gcc dot gnu.org
2021-02-24 17:00 ` cvs-commit at gcc dot gnu.org
2021-02-24 17:01 ` redi at gcc dot gnu.org
2021-03-23 11:12 ` redi at gcc dot gnu.org
2021-03-23 11:13 ` redi at gcc dot gnu.org
2021-03-23 11:14 ` jakub at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-98389-4-Zn24RznBX1@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).