From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 2/2] [gdb/build] Add Wno-error=stringop-overflow
Date: Wed, 28 Oct 2026 13:54:45 +0100 [thread overview]
Message-ID: <20261028125445.1745119-3-tdevries@suse.de> (raw)
In-Reply-To: <20261028125445.1745119-1-tdevries@suse.de>
Add Wno-error=stringop-overflow to the build warning setup, to account for the
fact that it's likely to have false positives [1].
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443
---
gdb/configure | 1 +
gdbserver/configure | 1 +
gdbsupport/configure | 1 +
gdbsupport/warning.m4 | 1 +
4 files changed, 4 insertions(+)
diff --git a/gdb/configure b/gdb/configure
index e747ffce49f..76ad40871a9 100755
--- a/gdb/configure
+++ b/gdb/configure
@@ -31159,6 +31159,7 @@ build_warnings=" \
-Wmissing-declarations \
-Wno-char-subscripts \
-Wno-error=deprecated-register \
+-Wno-error=stringop-overflow \
-Wno-mismatched-tags \
-Wno-sign-compare -Wno-error=maybe-uninitialized \
-Wno-switch \
diff --git a/gdbserver/configure b/gdbserver/configure
index e00e1e1c1c5..6c24a7b8fc0 100755
--- a/gdbserver/configure
+++ b/gdbserver/configure
@@ -12889,6 +12889,7 @@ build_warnings=" \
-Wmissing-declarations \
-Wno-char-subscripts \
-Wno-error=deprecated-register \
+-Wno-error=stringop-overflow \
-Wno-mismatched-tags \
-Wno-sign-compare -Wno-error=maybe-uninitialized \
-Wno-switch \
diff --git a/gdbsupport/configure b/gdbsupport/configure
index 7ed4e259ffe..882b91017ab 100755
--- a/gdbsupport/configure
+++ b/gdbsupport/configure
@@ -13892,6 +13892,7 @@ build_warnings=" \
-Wmissing-declarations \
-Wno-char-subscripts \
-Wno-error=deprecated-register \
+-Wno-error=stringop-overflow \
-Wno-mismatched-tags \
-Wno-sign-compare -Wno-error=maybe-uninitialized \
-Wno-switch \
diff --git a/gdbsupport/warning.m4 b/gdbsupport/warning.m4
index 3148feb740a..558fd2177da 100644
--- a/gdbsupport/warning.m4
+++ b/gdbsupport/warning.m4
@@ -47,6 +47,7 @@ build_warnings=" \
-Wmissing-declarations \
-Wno-char-subscripts \
-Wno-error=deprecated-register \
+-Wno-error=stringop-overflow \
-Wno-mismatched-tags \
-Wno-sign-compare -Wno-error=maybe-uninitialized \
-Wno-switch \
--
2.51.0
next prev parent reply other threads:[~2026-10-28 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 12:54 [PATCH 0/2] [gdb/build] Two Wstringop-overflow updates Tom de Vries
2026-10-28 12:54 ` [PATCH 1/2] [gdb/build] Fix Wstringop-overflow in selftests::vex2_to_vex3 Tom de Vries
2026-10-28 12:54 ` Tom de Vries [this message]
2026-10-28 16:23 ` [PATCH 0/2] [gdb/build] Two Wstringop-overflow updates Tom Tromey
2026-10-28 23:15 ` 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=20261028125445.1745119-3-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