linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/3] perf bench: Avoid NDEBUG warning
Date: Thu, 30 Mar 2023 18:11:35 -0300	[thread overview]
Message-ID: <ZCX7B/7ikbbie/FD@kernel.org> (raw)
In-Reply-To: <20230330183827.1412303-1-irogers@google.com>

Em Thu, Mar 30, 2023 at 11:38:25AM -0700, Ian Rogers escreveu:
> With NDEBUG set the asserts are compiled out. This yields
> "unused-but-set-variable" variables. Move these variables behind
> NDEBUG to avoid the warning.

Thanks, applied.

- Arnaldo

 
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
>  tools/perf/bench/find-bit-bench.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/perf/bench/find-bit-bench.c b/tools/perf/bench/find-bit-bench.c
> index d103c3136983..7e25b0e413f6 100644
> --- a/tools/perf/bench/find-bit-bench.c
> +++ b/tools/perf/bench/find-bit-bench.c
> @@ -61,7 +61,6 @@ static int do_for_each_set_bit(unsigned int num_bits)
>  	double time_average, time_stddev;
>  	unsigned int bit, i, j;
>  	unsigned int set_bits, skip;
> -	unsigned int old;
>  
>  	init_stats(&fb_time_stats);
>  	init_stats(&tb_time_stats);
> @@ -73,7 +72,10 @@ static int do_for_each_set_bit(unsigned int num_bits)
>  			__set_bit(i, to_test);
>  
>  		for (i = 0; i < outer_iterations; i++) {
> -			old = accumulator;
> +#ifndef NDEBUG
> +			unsigned int old = accumulator;
> +#endif
> +
>  			gettimeofday(&start, NULL);
>  			for (j = 0; j < inner_iterations; j++) {
>  				for_each_set_bit(bit, to_test, num_bits)
> @@ -85,7 +87,9 @@ static int do_for_each_set_bit(unsigned int num_bits)
>  			runtime_us = diff.tv_sec * USEC_PER_SEC + diff.tv_usec;
>  			update_stats(&fb_time_stats, runtime_us);
>  
> +#ifndef NDEBUG
>  			old = accumulator;
> +#endif
>  			gettimeofday(&start, NULL);
>  			for (j = 0; j < inner_iterations; j++) {
>  				for (bit = 0; bit < num_bits; bit++) {
> -- 
> 2.40.0.348.gf938b09366-goog
> 

-- 

- Arnaldo

      parent reply	other threads:[~2023-03-30 21:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 18:38 [PATCH v1 1/3] perf bench: Avoid NDEBUG warning Ian Rogers
2023-03-30 18:38 ` [PATCH v1 2/3] perf block-range: Move debug code behind ifndef NDEBUG Ian Rogers
2023-03-30 18:38 ` [PATCH v1 3/3] perf build: Conditionally define NDEBUG Ian Rogers
2023-03-30 21:11 ` Arnaldo Carvalho de Melo [this message]

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=ZCX7B/7ikbbie/FD@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=seanjc@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;
as well as URLs for NNTP newsgroup(s).