From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] [gdb/testsuite] Handle gcc 16
Date: Fri, 29 May 2026 14:51:47 +0200 [thread overview]
Message-ID: <20260529125149.2027857-1-tdevries@suse.de> (raw)
System gcc on fedora 44 (aarch64-linux) got bumped to 16, which defaults to
c++20 by default.
There are a number of new warnings. Fix them.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34187
Tom de Vries (2):
[gdb/testsuite] Fix ambiguous operator warning
[gdb/testsuite] Use Wno-non-c-typedef-for-linkage for gcc 16
gdb/testsuite/gdb.cp/class2.exp | 3 ++-
gdb/testsuite/gdb.cp/classes.exp | 9 ++++++---
gdb/testsuite/gdb.cp/cmpd-minsyms.cc | 2 +-
gdb/testsuite/gdb.cp/cmpd-minsyms.exp | 2 +-
gdb/testsuite/gdb.cp/many-args.cc | 2 +-
5 files changed, 11 insertions(+), 7 deletions(-)
base-commit: 2786cbfa05e3df7f8727eff02a15906eb244aa37
--
2.51.0
next reply other threads:[~2026-05-29 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 12:51 Tom de Vries [this message]
2026-05-29 12:51 ` [PATCH 1/2] [gdb/testsuite] Fix ambiguous operator warning Tom de Vries
2026-05-29 16:23 ` Keith Seitz
2026-05-29 12:51 ` [PATCH 2/2] [gdb/testsuite] Use Wno-non-c-typedef-for-linkage for gcc 16 Tom de Vries
2026-05-29 16:25 ` Keith Seitz
2026-05-30 8:49 ` Tom de Vries
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=20260529125149.2027857-1-tdevries@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.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