https://gcc.gnu.org/g:6e25ca387fbbb412a2e498e28ea5db28e033a318

commit r15-277-g6e25ca387fbbb412a2e498e28ea5db28e033a318
Author: Jonathan Wakely <jwak...@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.

Diff:
---
 libstdc++-v3/testsuite/util/testsuite_abi.cc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/libstdc++-v3/testsuite/util/testsuite_abi.cc 
b/libstdc++-v3/testsuite/util/testsuite_abi.cc
index e4bf3cdc8e0..ec7c3df9ecc 100644
--- a/libstdc++-v3/testsuite/util/testsuite_abi.cc
+++ b/libstdc++-v3/testsuite/util/testsuite_abi.cc
@@ -254,8 +254,8 @@ check_version(symbol& test, bool added)
        test.version_status = symbol::incompatible;
 
       // Check that added symbols are added in the latest pre-release version.
-      bool latestp = (test.version_name == "GLIBCXX_3.4.33"
-                    || test.version_name == "CXXABI_1.3.15"
+      bool latestp = (test.version_name == "GLIBCXX_3.4.34"
+                    || test.version_name == "CXXABI_1.3.16"
                     || test.version_name == "CXXABI_FLOAT128"
                     || test.version_name == "CXXABI_TM_1");
       if (added && !latestp)

Reply via email to