From: sdf@google.com
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, yhs@fb.com,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH bpf-next] libbpf: hashmap.h update to fix build issues using LLVM14
Date: Thu, 10 Nov 2022 17:25:26 -0800 [thread overview]
Message-ID: <Y22khvpDYu639yom@google.com> (raw)
In-Reply-To: <20221110223240.1350810-1-eddyz87@gmail.com>
On 11/11, Eduard Zingerman wrote:
> A fix for the LLVM compilation error while building bpftool.
> Replaces the expression:
> _Static_assert((p) == NULL || ...)
> by expression:
> _Static_assert((__builtin_constant_p((p)) ? (p) == NULL : 0) || ...)
IIUC, when __builtin_constant_p(p) returns false, we just ignore the NULL
check?
Do we have cases like that? If no, maybe it's safer to fail?
s/(p) == NULL : 0/(p) == NULL : 1/ ?
> When "p" is not a constant the former is not considered to be a
> constant expression by LLVM 14.
> The error was introduced in the following patch-set: [1].
> The error was reported here: [2].
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Eduard Zingerman <eddyz87@gmail.com>
> [1] https://lore.kernel.org/bpf/20221109142611.879983-1-eddyz87@gmail.com/
> [2] https://lore.kernel.org/all/202211110355.BcGcbZxP-lkp@intel.com/
> ---
> tools/lib/bpf/hashmap.h | 3 ++-
> tools/perf/util/hashmap.h | 3 ++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
> diff --git a/tools/lib/bpf/hashmap.h b/tools/lib/bpf/hashmap.h
> index 3fe647477bad..0a5bf1937a7c 100644
> --- a/tools/lib/bpf/hashmap.h
> +++ b/tools/lib/bpf/hashmap.h
> @@ -123,7 +123,8 @@ enum hashmap_insert_strategy {
> };
> #define hashmap_cast_ptr(p) ({ \
> - _Static_assert((p) == NULL || sizeof(*(p)) == sizeof(long), \
> + _Static_assert((__builtin_constant_p((p)) ? (p) == NULL : 0) || \
> + sizeof(*(p)) == sizeof(long), \
> #p " pointee should be a long-sized integer or a pointer"); \
> (long *)(p); \
> })
> diff --git a/tools/perf/util/hashmap.h b/tools/perf/util/hashmap.h
> index 3fe647477bad..0a5bf1937a7c 100644
> --- a/tools/perf/util/hashmap.h
> +++ b/tools/perf/util/hashmap.h
> @@ -123,7 +123,8 @@ enum hashmap_insert_strategy {
> };
> #define hashmap_cast_ptr(p) ({ \
> - _Static_assert((p) == NULL || sizeof(*(p)) == sizeof(long), \
> + _Static_assert((__builtin_constant_p((p)) ? (p) == NULL : 0) || \
> + sizeof(*(p)) == sizeof(long), \
> #p " pointee should be a long-sized integer or a pointer"); \
> (long *)(p); \
> })
> --
> 2.34.1
next prev parent reply other threads:[~2022-11-11 1:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 22:32 [PATCH bpf-next] libbpf: hashmap.h update to fix build issues using LLVM14 Eduard Zingerman
2022-11-11 1:25 ` sdf [this message]
2022-11-11 1:34 ` sdf
2022-11-11 1:44 ` Eduard Zingerman
2022-11-11 17:19 ` sdf
2022-11-11 18:30 ` Andrii Nakryiko
2022-11-11 1:51 ` Eduard Zingerman
2022-11-11 18:40 ` patchwork-bot+netdevbpf
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=Y22khvpDYu639yom@google.com \
--to=sdf@google.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=lkp@intel.com \
--cc=yhs@fb.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