public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/108882] New: [13 Regression] Wrong symver on 4 new libstdc++ symbols on ppc64le Date: Wed, 22 Feb 2023 09:35:15 +0000 [thread overview] Message-ID: <bug-108882-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108882 Bug ID: 108882 Summary: [13 Regression] Wrong symver on 4 new libstdc++ symbols on ppc64le Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- As mentioned in https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612342.html , I think r13-3888-gb3ac43a3c05744d62a9 has added FUNC:_ZSt15__try_use_facetINSt19__gnu_cxx11_ieee1289money_getIcSt19istreambuf_iteratorIcSt11char_traitsIcEEEEEPKT_RKSt6locale@@GLIBCXX_3.4.31 FUNC:_ZSt15__try_use_facetINSt19__gnu_cxx11_ieee1289money_getIwSt19istreambuf_iteratorIwSt11char_traitsIwEEEEEPKT_RKSt6locale@@GLIBCXX_3.4.31 FUNC:_ZSt15__try_use_facetINSt19__gnu_cxx11_ieee1289money_putIcSt19ostreambuf_iteratorIcSt11char_traitsIcEEEEEPKT_RKSt6locale@@GLIBCXX_3.4.31 FUNC:_ZSt15__try_use_facetINSt19__gnu_cxx11_ieee1289money_putIwSt19ostreambuf_iteratorIwSt11char_traitsIwEEEEEPKT_RKSt6locale@@GLIBCXX_3.4.31 symbols which at least for consistency with all other __gnu_cxx11_ieee128 symbols should be IMHO in GLIBCXX_IEEE128_3.4.31 symver rather than GLIBCXX_3.4.31.
next reply other threads:[~2023-02-22 9:35 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-22 9:35 jakub at gcc dot gnu.org [this message] 2023-02-22 9:35 ` [Bug libstdc++/108882] " jakub at gcc dot gnu.org 2023-02-22 11:42 ` redi at gcc dot gnu.org 2023-03-07 17:35 ` cvs-commit at gcc dot gnu.org 2023-03-07 17:49 ` redi at gcc dot gnu.org 2023-03-07 18:49 ` redi at gcc dot gnu.org 2023-03-09 16:12 ` cvs-commit at gcc dot gnu.org 2023-03-10 18:16 ` 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-108882-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).