Dwarves debugging tools
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: dwarves@vger.kernel.org
Subject: Re: [PATCH] Avoid warning when building with NDEBUG
Date: Thu, 18 Feb 2021 16:21:40 -0300	[thread overview]
Message-ID: <YC6+RO9ayyGq45FK@kernel.org> (raw)
In-Reply-To: <20210218175115.2850050-1-irogers@google.com>

Em Thu, Feb 18, 2021 at 09:51:15AM -0800, Ian Rogers escreveu:
> The assert macro is compiled out with NDEBUG which can lead to an unused
> variable warning if the variable is only read in the assert. This is
> seen just here:
> 
> dwarf_loader.c:957:17: error: unused variable 'tag' [-Werror,-Wunused-variable]
>         const uint16_t tag = dwarf_tag(die);

Thanks Ian, I added:

Signed-off-by: Ian Rogers <irogers@google.com>

And CC: dwarves@vger.kernel.org

Please let me know if this is all ok.

- Arnaldo

> ---
>  dwarf_loader.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/dwarf_loader.c b/dwarf_loader.c
> index b73d786..22c3a55 100644
> --- a/dwarf_loader.c
> +++ b/dwarf_loader.c
> @@ -954,9 +954,10 @@ static struct lexblock *lexblock__new(Dwarf_Die *die, struct cu *cu)
>  
>  static void ftype__init(struct ftype *ftype, Dwarf_Die *die, struct cu *cu)
>  {
> +#ifndef NDEBUG
>  	const uint16_t tag = dwarf_tag(die);
>  	assert(tag == DW_TAG_subprogram || tag == DW_TAG_subroutine_type);
> -
> +#endif
>  	tag__init(&ftype->tag, cu, die);
>  	INIT_LIST_HEAD(&ftype->parms);
>  	ftype->nr_parms	    = 0;
> -- 
> 2.30.0.617.g56c4b15f3c-goog
> 

-- 

- Arnaldo

       reply	other threads:[~2021-02-18 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210218175115.2850050-1-irogers@google.com>
2021-02-18 19:21 ` Arnaldo Carvalho de Melo [this message]
2021-02-18 19:34   ` [PATCH] Avoid warning when building with NDEBUG Ian Rogers
2021-02-18 19:43     ` Arnaldo Carvalho de Melo

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=YC6+RO9ayyGq45FK@kernel.org \
    --to=acme@kernel.org \
    --cc=dwarves@vger.kernel.org \
    --cc=irogers@google.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