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++/114692] [14 Regression] Symbol versioning problem in GCC 14 libstdc++.so.6
Date: Tue, 14 May 2024 09:50:46 +0000	[thread overview]
Message-ID: <bug-114692-4-04Rqr9OXvP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114692-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-14 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:

https://gcc.gnu.org/g:788ccd269e0c32c33ce0c1359137fe1b35dc7a2d

commit r14-10205-g788ccd269e0c32c33ce0c1359137fe1b35dc7a2d
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Apr 11 15:35:11 2024 +0100

    libstdc++: Update ABI test to disallow adding to released symbol versions

    If we update the list of "active" symbols versions now, rather than when
    adding a new symbol version, we will notice if new symbols get added to
    the wrong version (as in PR 114692).

    libstdc++-v3/ChangeLog:

            * testsuite/util/testsuite_abi.cc: Update latest versions to
            new versions that should be used in future.

    (cherry picked from commit 6e25ca387fbbb412a2e498e28ea5db28e033a318)

      parent reply	other threads:[~2024-05-14  9:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 11:20 [Bug libstdc++/114692] New: " jakub at gcc dot gnu.org
2024-04-11 11:20 ` [Bug libstdc++/114692] " jakub at gcc dot gnu.org
2024-04-11 11:22 ` redi at gcc dot gnu.org
2024-04-11 11:27 ` redi at gcc dot gnu.org
2024-04-11 11:28 ` jakub at gcc dot gnu.org
2024-04-11 11:29 ` jakub at gcc dot gnu.org
2024-04-11 11:31 ` redi at gcc dot gnu.org
2024-04-11 11:31 ` redi at gcc dot gnu.org
2024-04-11 11:34 ` redi at gcc dot gnu.org
2024-04-11 11:37 ` jakub at gcc dot gnu.org
2024-04-11 11:46 ` jakub at gcc dot gnu.org
2024-04-11 13:52 ` redi at gcc dot gnu.org
2024-04-11 14:24 ` cvs-commit at gcc dot gnu.org
2024-04-11 14:24 ` redi at gcc dot gnu.org
2024-05-07 12:46 ` cvs-commit at gcc dot gnu.org
2024-05-14  9:50 ` cvs-commit at gcc dot gnu.org [this message]

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-114692-4-04Rqr9OXvP@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).