On Wed, 7 Jan 2026 at 14:18, Frank Scheiner <[email protected]> wrote: > > On 07.01.26 14:10, Jonathan Wakely wrote: > > On Wed, 7 Jan 2026 at 12:58, Frank Scheiner wrote: > >> > >> === libstdc++ Summary === > >> > >> # of expected passes 18162 19243 > >> # of unexpected failures 9 245 > >> # of expected failures 131 140 > >> # of unresolved testcases 2 > >> # of unsupported tests 740 786 > >> ``` > >> > >> Overall this looks like an improvement to me. Although the number of > >> unexpected failures for libstdc++ increased dramatically. But the number > >> of expected passes - where they increased - increased more than the > >> number of failures. > > > > Is there a pattern to the unexpected failures? Are they all in a > > particular part of the library? Are they compilation failures? ICEs? > > failed assertions in the tests at runtime? > > I also looked into the details for: > > * libstdc++ (FAIL also present for GCC 15.1.0, but might be relevant) > * 18_support > * 19_diagnostics > > ...so far. > > In the following the failing test and the related error/info message > below: > > ``` > FAIL: libstdc++-abi/abi_check
You probably need to update the ABI baseline in config/abi/post/ia64-linux-gnu/baseline_symbols.txt Run 'make new-abi-baseline ' in the libstdc++-v3 buid dir, then move the baseline_symbolds.txt.new file to replace baseline_symbols.txt > => > [...] ## more info about symbols available > # of added symbols: 148 > # of missing symbols: 0 > # of undesignated symbols: 2 > # of incompatible symbols: 112 > > FAIL: 18_support/bad_alloc/cons_virtual_derivation.cc -std=gnu++17 execution > test > => > '__gnu_test::diamond_derivation_base<std::bad_alloc, > true>::diamond_derivation_error' > > FAIL: 18_support/bad_cast/cons_virtual_derivation.cc -std=gnu++17 execution > test > => > '__gnu_test::diamond_derivation_base<std::bad_cast, > true>::diamond_derivation_error' > > FAIL: 18_support/bad_exception/cons_virtual_derivation.cc -std=gnu++17 > execution test > => > '__gnu_test::diamond_derivation_base<std::bad_exception, > true>::diamond_derivation_error' > > FAIL: 18_support/bad_typeid/cons_virtual_derivation.cc -std=gnu++17 > execution test > => > '__gnu_test::diamond_derivation_base<std::bad_typeid, > true>::diamond_derivation_error' > > FAIL: 18_support/nested_exception/rethrow_if_nested.cc -std=gnu++17 > execution test > => > no error shown, maybe timed out That would show "WARNING: program timed out" No error usually means it segfaulted. > > FAIL: 19_diagnostics/logic_error/cons_virtual_derivation.cc -std=gnu++17 > execution test > => > '__gnu_test::diamond_derivation_base<std::logic_error, > false>::diamond_derivation_error' > > FAIL: 19_diagnostics/runtime_error/cons_virtual_derivation.cc -std=gnu++17 > execution test > => > '__gnu_test::diamond_derivation_base<std::runtime_error, > false>::diamond_derivation_error' > > FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++26 execution test > => > /dev/shm/gcc-16-20251214/libstdc++-v3/testsuite/19_diagnostics/stacktrace/stacktrace.cc:313: > void test_assign(): Assertion 's0.at(0).source_line() == > s0.get_allocator().get_personality()' failed. > > FAIL: 19_diagnostics/system_error/cons_virtual_derivation.cc -std=gnu++17 > execution test > => > '__gnu_test::diamond_derivation_base<std::system_error, > true>::diamond_derivation_error' > ``` > > Cheers, > Frank >
