Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH] Add two new warnings to warning.m4
Date: Wed,  3 Jun 2026 13:05:14 -0600	[thread overview]
Message-ID: <20260603190514.333176-1-tromey@adacore.com> (raw)

I recently learned that GCC has improved -Wdangling-reference and
added -Wunterminated-string-initialization.  Both of these seem
sensible to me, so this patch adds them to warning.m4.

gdb rebuilds cleanly with this in place on x86-64 Fedora 43.
---
 gdb/configure         | 2 ++
 gdbserver/configure   | 2 ++
 gdbsupport/configure  | 2 ++
 gdbsupport/warning.m4 | 2 ++
 4 files changed, 8 insertions(+)

diff --git a/gdb/configure b/gdb/configure
index 17c95930f60..80931d10bef 100755
--- a/gdb/configure
+++ b/gdb/configure
@@ -31580,6 +31580,7 @@ fi
 # The options we'll try to enable.
 build_warnings=" \
 -Wall \
+-Wdangling-reference \
 -Wdeprecated-copy \
 -Wdeprecated-copy-dtor \
 -Wduplicated-cond \
@@ -31597,6 +31598,7 @@ build_warnings=" \
 -Wshadow=local \
 -Wstrict-null-sentinel \
 -Wsuggest-override \
+-Wunterminated-string-initialization \
 -Wunused-but-set-parameter \
 -Wunused-but-set-variable \
 -Wunused-const-variable=1 \
diff --git a/gdbserver/configure b/gdbserver/configure
index 0159da6bdf4..46faecc3a20 100755
--- a/gdbserver/configure
+++ b/gdbserver/configure
@@ -13448,6 +13448,7 @@ fi
 # The options we'll try to enable.
 build_warnings=" \
 -Wall \
+-Wdangling-reference \
 -Wdeprecated-copy \
 -Wdeprecated-copy-dtor \
 -Wduplicated-cond \
@@ -13465,6 +13466,7 @@ build_warnings=" \
 -Wshadow=local \
 -Wstrict-null-sentinel \
 -Wsuggest-override \
+-Wunterminated-string-initialization \
 -Wunused-but-set-parameter \
 -Wunused-but-set-variable \
 -Wunused-const-variable=1 \
diff --git a/gdbsupport/configure b/gdbsupport/configure
index 584a80ef825..0bc9ff1db9a 100755
--- a/gdbsupport/configure
+++ b/gdbsupport/configure
@@ -14123,6 +14123,7 @@ fi
 # The options we'll try to enable.
 build_warnings=" \
 -Wall \
+-Wdangling-reference \
 -Wdeprecated-copy \
 -Wdeprecated-copy-dtor \
 -Wduplicated-cond \
@@ -14140,6 +14141,7 @@ build_warnings=" \
 -Wshadow=local \
 -Wstrict-null-sentinel \
 -Wsuggest-override \
+-Wunterminated-string-initialization \
 -Wunused-but-set-parameter \
 -Wunused-but-set-variable \
 -Wunused-const-variable=1 \
diff --git a/gdbsupport/warning.m4 b/gdbsupport/warning.m4
index 718ac34aa3c..3148feb740a 100644
--- a/gdbsupport/warning.m4
+++ b/gdbsupport/warning.m4
@@ -38,6 +38,7 @@ fi
 # The options we'll try to enable.
 build_warnings=" \
 -Wall \
+-Wdangling-reference \
 -Wdeprecated-copy \
 -Wdeprecated-copy-dtor \
 -Wduplicated-cond \
@@ -55,6 +56,7 @@ build_warnings=" \
 -Wshadow=local \
 -Wstrict-null-sentinel \
 -Wsuggest-override \
+-Wunterminated-string-initialization \
 -Wunused-but-set-parameter \
 -Wunused-but-set-variable \
 -Wunused-const-variable=1 \

base-commit: 663cb9c0428068165fc98675599442163d302d41
-- 
2.54.0


             reply	other threads:[~2026-06-03 19:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03 19:05 Tom Tromey [this message]
2026-06-05  7:38 ` Tom de Vries
2026-06-05  7:41   ` Tom de Vries
2026-06-05 20:51   ` Tom Tromey
2026-06-05 21:13     ` 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=20260603190514.333176-1-tromey@adacore.com \
    --to=tromey@adacore.com \
    --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