From: Helge Deller <deller@gmx.de>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: arch/parisc/net/bpf_jit_comp32.c:321:13: sparse: sparse: missing identifier in declaration
Date: Fri, 17 Nov 2023 14:16:00 +0100 [thread overview]
Message-ID: <a13df827-cd2c-481f-87ed-719936b96c41@gmx.de> (raw)
In-Reply-To: <202311172127.5PEz8XzL-lkp@intel.com>
On 11/17/23 14:07, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 7475e51b87969e01a6812eac713a1c8310372e8a
> commit: 4800a6215e335c6dade05e10c8fdbf919c04a3a7 parisc: Wire up eBPF JIT compiler
> date: 3 months ago
> config: parisc-randconfig-r113-20231115 (https://download.01.org/0day-ci/archive/20231117/202311172127.5PEz8XzL-lkp@intel.com/config)
> compiler: hppa-linux-gcc (GCC) 13.2.0
> reproduce: (https://download.01.org/0day-ci/archive/20231117/202311172127.5PEz8XzL-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/202311172127.5PEz8XzL-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);
This is actually a sparse bug.... "$" is a valid character with which function
names may start with (at least on parisc).
Helge
next prev parent reply other threads:[~2023-11-17 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 13:07 kernel test robot
2023-11-17 13:16 ` Helge Deller [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-17 7:46 kernel test robot
2023-11-16 21:00 kernel test robot
2023-11-16 12:18 kernel test robot
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=a13df827-cd2c-481f-87ed-719936b96c41@gmx.de \
--to=deller@gmx.de \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®