https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112630
Bug ID: 112630
Summary: [14 Regression] 19_diagnostics/stacktrace/output.cc
execution test
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: testsuite-fail
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: hp at gcc dot gnu.org
CC: redi at gcc dot gnu.org
Target Milestone: ---
Target: cris-elf, m68k-linux-gnu, arm
>From r14-5536-g23725aa53bd264, this test started failing for cris-elf and some
other targets.
The test changed from "dg-compile" to "dg-run" so for once there's a simple
cause for the regression, and N.B. I notably disregard the underlying problem
that the test actually fails when running; a problem that doesn't seem trivial.
Incidentally, for cris-elf as well as (at least) m68k-linux-gnu, the
neighboring stacktrace execution tests fail (excerpt for cris-elf at
r14-5540-ga671095c208c):
Running /x/gcc/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ...
FAIL: 19_diagnostics/stacktrace/current.cc -std=gnu++23 execution test
FAIL: 19_diagnostics/stacktrace/current.cc -std=gnu++26 execution test
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
FAIL: 23_containers/vector/debug/mutex_association.cc -std=gnu++17 execution
test
FAIL: 27_io/basic_ostream/inserters_arithmetic/char/hexfloat.cc -std=gnu++17
execution test
[...]
To wit, of those, these are the introduced regressions:
FAIL: 19_diagnostics/stacktrace/output.cc -std=gnu++23 execution test
FAIL: 19_diagnostics/stacktrace/output.cc -std=gnu++26 execution test
For the other targets, compare results for m68k-linux:
https://gcc.gnu.org/pipermail/gcc-testresults/2023-November/801238.html
...to its earlier results:
https://gcc.gnu.org/pipermail/gcc-testresults/2023-November/800388.html
The "arm" CI bot picked it up too:
https://gcc.gnu.org/pipermail/gcc-regression/2023-November/078553.html
I'm not sure which component fits best here. It seems there's an exposed bug
with libstdc++ or libbacktrace or both. Or, it could just be that the change
from dg-compile to dg-run is a testsuite typo; that it shouldn't dg-run.
