diff options
| author | Simon Marchi <simon.marchi@efficios.com> | 2020-02-11 10:51:49 -0500 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@efficios.com> | 2020-02-11 10:51:49 -0500 |
| commit | 8ddd8e0ed83ce09671695540788645e54b2b09a5 (patch) | |
| tree | fcf2901f171d0d955fb334732b586c7ca4f72be8 /gdbsupport/warning.m4 | |
| parent | 58df732b2166c31c8ee868b95cb62ef232e25387 (diff) | |
| download | gdb-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 'gdbsupport/warning.m4')
| -rw-r--r-- | gdbsupport/warning.m4 | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/gdbsupport/warning.m4 b/gdbsupport/warning.m4 index e2b8a43..81939ed 100644 --- a/gdbsupport/warning.m4 +++ b/gdbsupport/warning.m4 @@ -50,7 +50,9 @@ build_warnings="-Wall -Wpointer-arith \ -Wdeprecated-copy \ -Wdeprecated-copy-dtor \ -Wredundant-move \ --Wmissing-declarations" +-Wmissing-declarations \ +-Wstrict-null-sentinel \ +" case "${host}" in *-*-mingw32*) |