From: kernel test robot <lkp@intel.com>
To: Luis Gerhorst <luis.gerhorst@fau.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Alexei Starovoitov <ast@kernel.org>
Subject: [linux-next:master 1327/3035] arch/powerpc/net/bpf_jit_comp64.c:417:21: warning: variable 'ori31_emitted' set but not used
Date: Wed, 18 Jun 2025 05:02:08 +0800 [thread overview]
Message-ID: <202506180402.uUXwVoSH-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 4325743c7e209ae7845293679a4de94b969f2bef
commit: dff883d9e93a7f2f2fa4e38a9444b2c79d6da91a [1327/3035] bpf, arm64, powerpc: Change nospec to include v1 barrier
config: powerpc64-randconfig-002-20250618 (https://download.01.org/0day-ci/archive/20250618/202506180402.uUXwVoSH-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 875b36a8742437b95f623bab1e0332562c7b4b3f)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250618/202506180402.uUXwVoSH-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202506180402.uUXwVoSH-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/powerpc/net/bpf_jit_comp64.c:417:21: warning: variable 'ori31_emitted' set but not used [-Wunused-but-set-variable]
417 | bool sync_emitted, ori31_emitted;
| ^
1 warning generated.
vim +/ori31_emitted +417 arch/powerpc/net/bpf_jit_comp64.c
411
412 /* Assemble the body code between the prologue & epilogue */
413 int bpf_jit_build_body(struct bpf_prog *fp, u32 *image, u32 *fimage, struct codegen_context *ctx,
414 u32 *addrs, int pass, bool extra_pass)
415 {
416 enum stf_barrier_type stf_barrier = stf_barrier_type_get();
> 417 bool sync_emitted, ori31_emitted;
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-06-17 21:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202506180402.uUXwVoSH-lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luis.gerhorst@fau.de \
--cc=oe-kbuild-all@lists.linux.dev \
/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