https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111641
--- Comment #14 from dave.anglin at bell dot net --- On 2024-05-29 8:17 a.m., ro at CeBiTec dot Uni-Bielefeld.DE wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111641 > > --- Comment #13 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot > Uni-Bielefeld.DE> --- >> --- Comment #12 from dave.anglin at bell dot net --- >> It will be a few days before I can test. I've had three hard drives fail on >> my >> main hppa >> system in the past few weeks. > I guess it's best to postpone committing to the gcc-14 branch until you > can report hppa results then. Btw., when you're ready, could you also > check the libbacktrace test results (no .sum file, unfortunately, just > buried deeply in make check output) for comparison? Thanks. Change fixes the following libstdc++ tests on hppa-linux: 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 The libbacktrace tests all pass on hppa-linux.
