public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/98389] New: [11 regression] libstdc++-abi/abi_check fails after r11-6249 on powerpc64 big endian Date: Sat, 19 Dec 2020 07:09:00 +0000 [thread overview] Message-ID: <bug-98389-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98389 Bug ID: 98389 Summary: [11 regression] libstdc++-abi/abi_check fails after r11-6249 on powerpc64 big endian Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:3c57e692357c79ee7623dfc1586652aee2aefb8f, r11-6249: 89 failures FAIL: libstdc++-abi/abi_check This only fails on BE. The output from this is extensive and I am not positive that these are what cause the failures but they sound like possible failures: 2 undesignated symbols 0 _ZSt11__once_call std::__once_call version status: compatible GLIBCXX_3.4.11 type: tls type size: 8 status: undesignated 1 _ZSt15__once_callable std::__once_callable version status: compatible GLIBCXX_3.4.11 type: tls type size: 8 status: undesignated 3 incompatible symbols 0 _ZSt8to_charsPcS_g std::to_chars(char*, char*, __float128) version status: incompatible GLIBCXX_3.4.29 type: function status: added 1 _ZSt8to_charsPcS_gSt12chars_format std::to_chars(char*, char*, __float128, std::chars_format) version status: incompatible GLIBCXX_3.4.29 type: function status: added 2 _ZSt8to_charsPcS_gSt12chars_formati std::to_chars(char*, char*, __float128, std::chars_format, int) version status: incompatible GLIBCXX_3.4.29 type: function status: added ==== libstdc++-v3 check-abi Summary ==== # of added symbols: 109 # of missing symbols: 0 # of undesignated symbols: 2 # of incompatible symbols: 3 using: baseline_symbols.txt FAIL: libstdc++-abi/abi_check
next reply other threads:[~2020-12-19 7:09 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-19 7:09 seurer at gcc dot gnu.org [this message] 2020-12-19 9:01 ` [Bug libstdc++/98389] " schwab@linux-m68k.org 2020-12-19 13:58 ` redi at gcc dot gnu.org 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@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: linkBe 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).