public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <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: Tue, 04 Jun 2024 07:10:41 +0000 [thread overview]
Message-ID: <bug-111641-4-gJV5jNJgdP@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 #16 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-14 branch has been updated by Rainer Orth <ro@gcc.gnu.org>:
https://gcc.gnu.org/g:d92b508dd19daffedfc0fb02e5bfa710f2c397b0
commit r14-10274-gd92b508dd19daffedfc0fb02e5bfa710f2c397b0
Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date: Wed May 29 10:08:07 2024 +0200
libstdc++: Build libbacktrace and 19_diagnostics/stacktrace with
-funwind-tables [PR111641]
Several of the 19_diagnostics/stacktrace tests FAIL on Solaris/SPARC (32
and 64-bit), Solaris/x86 (32-bit only), and several other targets:
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
As it turns out, both the copy of libbacktrace in libstdc++ and the
testcases proper need to compiled with -funwind-tables, as is done for
libbacktrace itself.
This isn't an issue on Linux/x86_64 and Solaris/amd64 since 64-bit x86
always defaults to -funwind-tables. 32-bit x86 does, too, when
-fomit-frame-pointer is enabled as on Linux/i686, but unlike
Solaris/i386.
So this patch always enables the option both for the libbacktrace copy
and the testcases.
Tested on i386-pc-solaris2.11, sparc-sun-solaris2.11, and
x86_64-pc-linux-gnu.
2024-05-23 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
libstdc++-v3:
PR libstdc++/111641
* src/libbacktrace/Makefile.am (AM_CFLAGS): Add -funwind-tables.
* src/libbacktrace/Makefile.in: Regenerate.
* testsuite/19_diagnostics/stacktrace/current.cc (dg-options): Add
-funwind-tables.
* testsuite/19_diagnostics/stacktrace/entry.cc: Likewise.
* testsuite/19_diagnostics/stacktrace/hash.cc: Likewise.
* testsuite/19_diagnostics/stacktrace/output.cc: Likewise.
* testsuite/19_diagnostics/stacktrace/stacktrace.cc: Likewise.
(cherry picked from commit a99ebb88f8f25e76ebed5afc22e64fa77a2f0d3f)
next prev parent reply other threads:[~2024-06-04 7:10 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
2024-06-04 7:10 ` cvs-commit at gcc dot gnu.org [this message]
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-gJV5jNJgdP@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).