All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org, bpf <bpf@vger.kernel.org>,
	Andrei Vagin <avagin@google.com>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: next: perf: 32-bit: bench/sched-seccomp-notify.c:139:24: error: format '%lu' expects argument of type 'long unsigned int', but argument 2 has type 'uint64_t'
Date: Mon, 3 Jul 2023 12:16:55 -0700	[thread overview]
Message-ID: <202307031216.171373CD3@keescook> (raw)
In-Reply-To: <CA+G9fYt1ZtucYds=p-Z+4sZ+nHMeEAFh2Fbe63VS_03-UsRwBg@mail.gmail.com>

On Mon, Jul 03, 2023 at 12:55:59PM +0530, Naresh Kamboju wrote:
> Following build regressions noticed on Linux next-20230703.
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> Regressions found on i386:
> 
>   - build/gcc-11-lkftconfig-perf
> 
> Regressions found on arm:
> 
>   - build/gcc-10-lkftconfig-perf
>   - build/gcc-11-lkftconfig-perf
> 
> Build error:
> =======
> bench/sched-seccomp-notify.c: In function 'bench_sched_seccomp_notify':
> bench/sched-seccomp-notify.c:139:24: error: format '%lu' expects
> argument of type 'long unsigned int', but argument 2 has type
> 'uint64_t' {aka 'long long unsigned int'} [-Werror=format=]
>   139 |   printf("# Executed %lu system calls\n\n",
>       |                      ~~^
>       |                        |
>       |                        long unsigned int
>       |                      %llu
>   140 |    loops);
>       |    ~~~~~
>       |    |
>       |    uint64_t {aka long long unsigned int}
> cc1: all warnings being treated as errors
> make[4]: *** [tools/build/Makefile.build:97:
> /home/tuxbuild/.cache/tuxmake/builds/1/build/bench/sched-seccomp-notify.o]
> Error 1

Thanks! I've updated the format string to use "%"PRIu64 now.

-Kees

> 
> Links:
>  - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230703/testrun/18069798/suite/build/test/gcc-10-lkftconfig-perf/history/
> 
> 
> --
> Linaro LKFT
> https://lkft.linaro.org

-- 
Kees Cook

      reply	other threads:[~2023-07-03 19:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03  7:25 next: perf: 32-bit: bench/sched-seccomp-notify.c:139:24: error: format '%lu' expects argument of type 'long unsigned int', but argument 2 has type 'uint64_t' Naresh Kamboju
2023-07-03 19:16 ` Kees Cook [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=202307031216.171373CD3@keescook \
    --to=keescook@chromium.org \
    --cc=acme@kernel.org \
    --cc=arnd@arndb.de \
    --cc=avagin@google.com \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.