public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/108882] [13 Regression] Wrong symver on 4 new libstdc++ symbols on ppc64le
Date: Tue, 07 Mar 2023 17:35:16 +0000	[thread overview]
Message-ID: <bug-108882-4-mAKSDt03nP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108882-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108882

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:7d30593c387e5feb0db8ad90d1650ee49361d536

commit r13-6531-g7d30593c387e5feb0db8ad90d1650ee49361d536
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Mar 7 14:19:36 2023 +0000

    libstdc++: Fix symver for __gnu_cxx11_ieee128::__try_use_facet [PR108882]

    libstdc++-v3/ChangeLog:

            PR libstdc++/108882
            * config/abi/pre/gnu.ver (GLIBCXX_3.4.31): Adjust patterns to
            not match symbols in namespace std::__gnu_cxx11_ieee128.
            * config/os/gnu-linux/ldbl-ieee128-extra.ver: Add patterns for
            std::__gnu_cxx11_ieee128::money_{get,put}.

  parent reply	other threads:[~2023-03-07 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22  9:35 [Bug libstdc++/108882] New: " jakub at gcc dot gnu.org
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 [this message]
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-mAKSDt03nP@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).