https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120567
--- Comment #7 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #6)
> What does the log show for that FAIL for cris-elf?
Totally different errors:
/x/libstdc++-v3/testsuite/19_diagnostics/stacktrace/entry.cc:39: void
test_members(): Assertion 'e1.source_line() == (__LINE__ - 5)' failed.
program stopped with signal 6 (Aborted).
FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++23 execution test
/x/libstdc++-v3/testsuite/19_diagnostics/stacktrace/output.cc:21: void
test_to_string(): Assertion 's1.contains("test_to_string()")' failed.
program stopped with signal 6 (Aborted).
FAIL: 19_diagnostics/stacktrace/output.cc -std=gnu++23 execution test
/x/libstdc++-v3/testsuite/19_diagnostics/stacktrace/stacktrace.cc:284: void
test_assign(): Assertion 's0.at(0).source_line() == (__LINE__ - 4)' failed.
program stopped with signal 6 (Aborted).
FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++23 execution test
I originally entered PR112630 when entry.c showed up as a regression, but you
wrote that was spurious. Since the stacktrace test failures aren't actually
regressions (they have always failed), I haven't looked at them, but for
context the current set is:
FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++23 execution test
FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++26 execution test
FAIL: 19_diagnostics/stacktrace/output.cc -std=gnu++23 execution test
FAIL: 19_diagnostics/stacktrace/output.cc -std=gnu++26 execution test
FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++23 execution test
FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++26 execution test
Since you asked! ;)
