aboutsummaryrefslogtreecommitdiff
path: root/gdb/configure
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@efficios.com>2020-02-11 10:51:49 -0500
committerSimon Marchi <simon.marchi@efficios.com>2020-02-11 10:51:49 -0500
commit8ddd8e0ed83ce09671695540788645e54b2b09a5 (patch)
treefcf2901f171d0d955fb334732b586c7ca4f72be8 /gdb/configure
parent58df732b2166c31c8ee868b95cb62ef232e25387 (diff)
downloadgdb-8ddd8e0ed83ce09671695540788645e54b2b09a5.zip
gdb-8ddd8e0ed83ce09671695540788645e54b2b09a5.tar.gz
gdb-8ddd8e0ed83ce09671695540788645e54b2b09a5.tar.bz2
Add -Wstrict-null-sentinel to gdbsupport/warning.m4
Commit 85f0dd3ce ("[gdb] Fix -Wstrict-null-sentinel warnings") fixed some violations of -Wstrict-null-sentinel. If we want to enforce this warning, I think we should enable it in our warning.m4 file. gdbsupport/ChangeLog: * warning.m4: Add -Wstrict-null-sentinel. * configure: Re-generate. gdbserver/ChangeLog: * configure: Re-generate. gdb/ChangeLog: * configure: Re-generate.
Diffstat (limited to 'gdb/configure')
-rwxr-xr-xgdb/configure3
1 files changed, 2 insertions, 1 deletions
diff --git a/gdb/configure b/gdb/configure
index a1d1506..2ce910c 100755
--- a/gdb/configure
+++ b/gdb/configure
@@ -16111,7 +16111,8 @@ build_warnings="-Wall -Wpointer-arith \
-Wdeprecated-copy \
-Wdeprecated-copy-dtor \
-Wredundant-move \
--Wmissing-declarations"
+-Wmissing-declarations \
+-Wstrict-null-sentinel"
case "${host}" in
*-*-mingw32*)