From: kernel test robot <lkp@intel.com>
To: Helge Deller <deller@gmx.de>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: arch/parisc/net/bpf_jit_comp32.c:321:13: sparse: sparse: missing identifier in declaration
Date: Thu, 16 Nov 2023 20:18:27 +0800 [thread overview]
Message-ID: <202311162045.0hHGIKOR-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: c42d9eeef8e5ba9292eda36fd8e3c11f35ee065c
commit: 4800a6215e335c6dade05e10c8fdbf919c04a3a7 parisc: Wire up eBPF JIT compiler
date: 3 months ago
config: parisc-randconfig-r113-20231115 (https://download.01.org/0day-ci/archive/20231116/202311162045.0hHGIKOR-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231116/202311162045.0hHGIKOR-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/202311162045.0hHGIKOR-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/parisc/net/bpf_jit_comp32.c:321:13: sparse: sparse: missing identifier in declaration
arch/parisc/net/bpf_jit_comp32.c:321:13: sparse: sparse: Expected ; at the end of type declaration
arch/parisc/net/bpf_jit_comp32.c:321:13: sparse: sparse: got $
arch/parisc/net/bpf_jit_comp32.c:322:13: sparse: sparse: Expected ; at the end of type declaration
arch/parisc/net/bpf_jit_comp32.c:322:13: sparse: sparse: got $
arch/parisc/net/bpf_jit_comp32.c:323:13: sparse: sparse: Expected ; at the end of type declaration
arch/parisc/net/bpf_jit_comp32.c:323:13: sparse: sparse: got $
arch/parisc/net/bpf_jit_comp32.c:666:37: sparse: sparse: Expected ) in function call
arch/parisc/net/bpf_jit_comp32.c:666:37: sparse: sparse: got $
arch/parisc/net/bpf_jit_comp32.c:669:37: sparse: sparse: Expected ) in function call
arch/parisc/net/bpf_jit_comp32.c:669:37: sparse: sparse: got $
arch/parisc/net/bpf_jit_comp32.c:672:37: sparse: sparse: Expected ) in function call
arch/parisc/net/bpf_jit_comp32.c:672:37: sparse: sparse: got $
>> arch/parisc/net/bpf_jit_comp32.c:666:36: sparse: sparse: not enough arguments for function emit_call_millicode
arch/parisc/net/bpf_jit_comp32.c:669:36: sparse: sparse: not enough arguments for function emit_call_millicode
arch/parisc/net/bpf_jit_comp32.c:672:36: sparse: sparse: not enough arguments for function emit_call_millicode
vim +321 arch/parisc/net/bpf_jit_comp32.c
ceb0e7267693d3 Helge Deller 2023-08-17 319
ceb0e7267693d3 Helge Deller 2023-08-17 320 /* extern hppa millicode functions */
ceb0e7267693d3 Helge Deller 2023-08-17 @321 extern void $$mulI(void);
ceb0e7267693d3 Helge Deller 2023-08-17 322 extern void $$divU(void);
ceb0e7267693d3 Helge Deller 2023-08-17 323 extern void $$remU(void);
ceb0e7267693d3 Helge Deller 2023-08-17 324
:::::: The code at line 321 was first introduced by commit
:::::: ceb0e7267693d3e6c43bd65695cd79d7c072a42a parisc: Add 32-bit eBPF JIT compiler
:::::: TO: Helge Deller <deller@gmx.de>
:::::: CC: Helge Deller <deller@gmx.de>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-11-16 12:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 12:18 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-16 21:00 arch/parisc/net/bpf_jit_comp32.c:321:13: sparse: sparse: missing identifier in declaration kernel test robot
2023-11-17 7:46 kernel test robot
2023-11-17 13:07 kernel test robot
2023-11-17 13:16 ` Helge Deller
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=202311162045.0hHGIKOR-lkp@intel.com \
--to=lkp@intel.com \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--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