From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Shunsuke Nakamura <nakamura.shun@fujitsu.com>,
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@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] libperf: Fix 32-bit build for tests uint64_t printf
Date: Tue, 1 Feb 2022 20:58:59 -0300 [thread overview]
Message-ID: <YfnJQ44BgtyIIBDw@kernel.org> (raw)
In-Reply-To: <20220201213903.699656-1-robh@kernel.org>
Em Tue, Feb 01, 2022 at 03:39:03PM -0600, Rob Herring escreveu:
> Commit a7f3713f6bf2 ("libperf tests: Add test_stat_multiplexing test")
> added printf's of 64-bit ints using %lu which doesn't work on 32-bit
> builds:
>
> tests/test-evlist.c:529:29: error: format ‘%lu’ expects argument of type \
> ‘long unsigned int’, but argument 4 has type ‘uint64_t’ {aka ‘long long unsigned int’} [-Werror=format=]
>
> Use PRIu64 instead which works on both 32-bit and 64-bit systems.
I´ll apply this tomorrow and as well will check why the existing tests
aren't catching this :-\
Thanks!
- Arnaldo
> Fixes: a7f3713f6bf2 ("libperf tests: Add test_stat_multiplexing test")
> Cc: Shunsuke Nakamura <nakamura.shun@fujitsu.com>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> tools/lib/perf/tests/test-evlist.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/tools/lib/perf/tests/test-evlist.c b/tools/lib/perf/tests/test-evlist.c
> index b3479dfa9a1c..fa854c83b7e7 100644
> --- a/tools/lib/perf/tests/test-evlist.c
> +++ b/tools/lib/perf/tests/test-evlist.c
> @@ -1,5 +1,6 @@
> // SPDX-License-Identifier: GPL-2.0
> #define _GNU_SOURCE // needed for sched.h to get sched_[gs]etaffinity and CPU_(ZERO,SET)
> +#include <inttypes.h>
> #include <sched.h>
> #include <stdio.h>
> #include <stdarg.h>
> @@ -526,12 +527,12 @@ static int test_stat_multiplexing(void)
>
> min = counts[0].val;
> for (i = 0; i < EVENT_NUM; i++) {
> - __T_VERBOSE("Event %2d -- Raw count = %lu, run = %lu, enable = %lu\n",
> + __T_VERBOSE("Event %2d -- Raw count = %" PRIu64 ", run = %" PRIu64 ", enable = %" PRIu64 "\n",
> i, counts[i].val, counts[i].run, counts[i].ena);
>
> perf_counts_values__scale(&counts[i], true, &scaled);
> if (scaled == 1) {
> - __T_VERBOSE("\t Scaled count = %lu (%.2lf%%, %lu/%lu)\n",
> + __T_VERBOSE("\t Scaled count = %" PRIu64 " (%.2lf%%, %" PRIu64 "/%" PRIu64 ")\n",
> counts[i].val,
> (double)counts[i].run / (double)counts[i].ena * 100.0,
> counts[i].run, counts[i].ena);
> --
> 2.32.0
--
- Arnaldo
prev parent reply other threads:[~2022-02-01 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 21:39 [PATCH] libperf: Fix 32-bit build for tests uint64_t printf Rob Herring
2022-02-01 23:58 ` 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=YfnJQ44BgtyIIBDw@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=nakamura.shun@fujitsu.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
/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).