From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "kernel test robot" <lkp@intel.com>,
"Alexei Starovoitov" <ast@kernel.org>
Cc: <oe-kbuild-all@lists.linux.dev>
Subject: Re: [linux-next:master 3430/4145] kernel/bpf/scev.c:736:33-42: duplicated argument to && or ||
Date: Sun, 08 Nov 2026 02:53:15 +0000 [thread overview]
Message-ID: <DMPHMZT0ORT5.3FFQQHE7YNP6J@gmail.com> (raw)
In-Reply-To: <202611080024.A0phXMMa-lkp@intel.com>
On Sat Nov 7, 2026 at 11:54 PM UTC, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: ddfe51b0a0f5dc9e415cc2c8ad8db17532dd426b
> commit: 28a373cb0f6a579049ffe92747575213a442673f [3430/4145] bpf: Fold sums of constants and two shifts by 32 in scalar evolution
> config: hexagon-randconfig-r2101-20261107 (https://download.01.org/0day-ci/archive/20261108/202611080024.A0phXMMa-lkp@intel.com/config)
> compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 0fa861dbbf46e5a75f621406fd91cb015d8754bf)
>
> 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/202611080024.A0phXMMa-lkp@intel.com/
>
> cocci warnings: (new ones prefixed by >>)
>>> kernel/bpf/scev.c:736:33-42: duplicated argument to && or ||
...
> 735 if (class == BPF_ALU64 && op == BPF_RSH && id >= 0 &&
> > 736 is_imm(scev, id, &imm) && imm == 32 &&
> 737 is_binop(scev, BPF_LSH, reg2expr[dst], &l, &r) &&
> 738 is_imm(scev, r, &imm) && imm == 32)
> 739 return replace_reg(scev, e, dst, expr1(scev, ZEXT32, l));
No. they are not duplicated, but yeah the coding style is questionable.
prev parent reply other threads:[~2026-11-08 2:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 23:54 [linux-next:master 3430/4145] kernel/bpf/scev.c:736:33-42: duplicated argument to && or || kernel test robot
2026-11-08 2:53 ` Alexei Starovoitov [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=DMPHMZT0ORT5.3FFQQHE7YNP6J@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=lkp@intel.com \
--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 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.