From: Yonghong Song <yonghong.song@linux.dev>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Kui-Feng Lee <sinquersw@gmail.com>
Cc: Thinker Li <thinker.li@gmail.com>,
kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Martin KaFai Lau <martin.lau@kernel.org>,
bpf <bpf@vger.kernel.org>
Subject: Re: [linux-next:master 5519/11156] kernel/bpf/bpf_struct_ops.c:247:16: warning: bitwise operation between different enumeration types ('enum bpf_type_flag' and 'enum bpf_reg_type')
Date: Sat, 2 Mar 2024 10:09:12 -0800 [thread overview]
Message-ID: <ef878388-ecef-45ff-a33a-d7b2e18d5220@linux.dev> (raw)
In-Reply-To: <CAADnVQJUZZXusOS3h9fnUUoFQ7=o5iJDDANaUqNBheuhHrUXeg@mail.gmail.com>
On 3/1/24 10:27 AM, Alexei Starovoitov wrote:
> On Fri, Mar 1, 2024 at 10:26 AM Kui-Feng Lee <sinquersw@gmail.com> wrote:
>> For BPF,
>>
>> We have a lot of code mixing bpf_type_flag and bpf_reg_type in bpf.
>> They cause the warning messages described in the message following.
>> Do we want to fix them all, or keep them as they are?
>>
>> They can be fixed by merging two enum types or casting here and there if
>> we want. Any other idea?
> We probably should add -Wno-enum-enum-conversion to kernel/bpf/Makefile instead.
The warnings are only triggered with latest llvm19 development branch.
The warnings are triggered in many subsystems, bpf, mm, etc.
The following commandline can workaround the issue:
make LLVM=1 -j KCFLAGS=-Wno-enum-enum-conversion
There is a discussion how to fix it here:
https://github.com/ClangBuiltLinux/linux/issues/2002
No conclusion yet.
prev parent reply other threads:[~2024-03-02 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 20:31 [linux-next:master 5519/11156] kernel/bpf/bpf_struct_ops.c:247:16: warning: bitwise operation between different enumeration types ('enum bpf_type_flag' and 'enum bpf_reg_type') kernel test robot
2024-02-29 21:07 ` Thinker Li
2024-03-01 18:25 ` Kui-Feng Lee
2024-03-01 18:27 ` Alexei Starovoitov
2024-03-02 18:09 ` Yonghong Song [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=ef878388-ecef-45ff-a33a-d7b2e18d5220@linux.dev \
--to=yonghong.song@linux.dev \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=martin.lau@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sinquersw@gmail.com \
--cc=thinker.li@gmail.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 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.