Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 3/3] Add -Wstrict-null-sentinel to gdbsupport/warning.m4
Date: Mon, 10 Feb 2020 16:42:00 -0000	[thread overview]
Message-ID: <CAPTJ0XGFpk_GMmV4J9nribYE1D8=LRb-LzUXWck6E95vvNCTkA@mail.gmail.com> (raw)
In-Reply-To: <20200210164024.32445-3-simon.marchi@efficios.com>

On Mon, Feb 10, 2020 at 10:40 AM Simon Marchi <simon.marchi@efficios.com> wrote:
>
> 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.
> ---
>  gdb/configure         | 3 ++-
>  gdbserver/configure   | 3 ++-
>  gdbsupport/configure  | 3 ++-
>  gdbsupport/warning.m4 | 3 ++-
>  4 files changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/gdb/configure b/gdb/configure
> index a1d150649729..2ce910c808ce 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*)
> diff --git a/gdbserver/configure b/gdbserver/configure
> index 4b9d7e3718fa..bd0e667af69b 100755
> --- a/gdbserver/configure
> +++ b/gdbserver/configure
> @@ -9815,7 +9815,8 @@ build_warnings="-Wall -Wpointer-arith \
>  -Wdeprecated-copy \
>  -Wdeprecated-copy-dtor \
>  -Wredundant-move \
> --Wmissing-declarations"
> +-Wmissing-declarations \
> +-Wstrict-null-sentinel"
>
>  case "${host}" in
>    *-*-mingw32*)
> diff --git a/gdbsupport/configure b/gdbsupport/configure
> index 197749b5d0ca..1f7d72cc5852 100755
> --- a/gdbsupport/configure
> +++ b/gdbsupport/configure
> @@ -10853,7 +10853,8 @@ build_warnings="-Wall -Wpointer-arith \
>  -Wdeprecated-copy \
>  -Wdeprecated-copy-dtor \
>  -Wredundant-move \
> --Wmissing-declarations"
> +-Wmissing-declarations \
> +-Wstrict-null-sentinel"
>
>  case "${host}" in
>    *-*-mingw32*)
> diff --git a/gdbsupport/warning.m4 b/gdbsupport/warning.m4
> index e2b8a43ddbd5..75bc21ca4261 100644
> --- a/gdbsupport/warning.m4
> +++ b/gdbsupport/warning.m4
> @@ -50,7 +50,8 @@ build_warnings="-Wall -Wpointer-arith \
>  -Wdeprecated-copy \
>  -Wdeprecated-copy-dtor \
>  -Wredundant-move \
> --Wmissing-declarations"
> +-Wmissing-declarations \
> +-Wstrict-null-sentinel"

Any thoughts on instead dong:
+-Wstrict-null-sentinel \
+"

so that future changes don't need to change the last line? Helps with blame too.

>
>  case "${host}" in
>    *-*-mingw32*)
> --
> 2.25.0
>


  reply	other threads:[~2020-02-10 16:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 16:40 [PATCH 1/3] gdbsupport: use AM_GDB_WARNINGS Simon Marchi
2020-02-10 16:40 ` [PATCH 3/3] Add -Wstrict-null-sentinel to gdbsupport/warning.m4 Simon Marchi
2020-02-10 16:42   ` Christian Biesinger via gdb-patches [this message]
2020-02-10 16:46     ` Simon Marchi
2020-02-11 14:57       ` Tom Tromey
2020-02-11 16:11         ` Simon Marchi
2020-02-10 16:40 ` [PATCH 2/3] Move gdb/warning.m4 to gdbsupport Simon Marchi
2020-02-11 14:55   ` Tom Tromey
2020-02-11 14:55 ` [PATCH 1/3] gdbsupport: use AM_GDB_WARNINGS Tom Tromey

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='CAPTJ0XGFpk_GMmV4J9nribYE1D8=LRb-LzUXWck6E95vvNCTkA@mail.gmail.com' \
    --to=gdb-patches@sourceware.org \
    --cc=cbiesinger@google.com \
    --cc=simon.marchi@efficios.com \
    /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