public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/111641] FAIL: 19_diagnostics/stacktrace/current.cc -std=gnu++23 execution test
Date: Mon, 03 Jun 2024 14:15:28 +0000 [thread overview]
Message-ID: <bug-111641-4-hM2VHmztOP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111641-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111641
--- Comment #15 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- 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.
Hi Dave,
thanks for checking. I guess it's reasonably safe to backport the patch
to the gcc-14 branch then.
next prev parent reply other threads:[~2024-06-03 14:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 14:49 [Bug libstdc++/111641] New: " danglin at gcc dot gnu.org
2023-09-29 15:09 ` [Bug libstdc++/111641] " redi at gcc dot gnu.org
2023-11-23 13:52 ` ro at gcc dot gnu.org
2023-11-23 16:36 ` redi at gcc dot gnu.org
2023-11-23 16:36 ` redi at gcc dot gnu.org
2024-05-22 14:24 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-23 8:36 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-23 9:26 ` ro at gcc dot gnu.org
2024-05-28 14:26 ` ro at gcc dot gnu.org
2024-05-29 8:08 ` cvs-commit at gcc dot gnu.org
2024-05-29 8:12 ` ro at gcc dot gnu.org
2024-05-29 9:36 ` redi at gcc dot gnu.org
2024-05-29 12:03 ` dave.anglin at bell dot net
2024-05-29 12:17 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-06-01 12:20 ` dave.anglin at bell dot net
2024-06-03 14:15 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2024-06-04 7:10 ` cvs-commit at gcc dot gnu.org
2024-06-04 7:11 ` ro at gcc dot gnu.org
2024-06-13 13:23 ` redi at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-111641-4-hM2VHmztOP@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).