From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: lib/crc/arm64/crc64-neon.h:14:9: sparse: sparse: Trying to use reserved word 'return' as identifier
Date: Thu, 09 Jul 2026 04:01:54 +0800 [thread overview]
Message-ID: <202607090311.fsN30k2z-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: lib/crc/arm64/crc64-neon.h:14:9: sparse: sparse: Trying to use reserved word 'return' as identifier"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Ard Biesheuvel <ardb@kernel.org>
CC: Eric Biggers <ebiggers@kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 0e35b9b6ec0ffcc5e23cbdec09f5c622ad532b53
commit: 061cef5fcee5a4bbaa8726f8c5fc1d5e2f89bff7 lib/crc: Turn NEON intrinsics crc64 implementation into common code
date: 6 weeks ago
:::::: branch date: 2 days ago
:::::: commit date: 6 weeks ago
config: arm64-randconfig-r112-20260708 (https://download.01.org/0day-ci/archive/20260709/202607090311.fsN30k2z-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260709/202607090311.fsN30k2z-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
| Fixes: 061cef5fcee5 ("lib/crc: Turn NEON intrinsics crc64 implementation into common code")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202607090311.fsN30k2z-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
lib/crc/crc64-neon.c: note: in included file (through arch/arm64/include/asm/neon-intrinsics.h):
/opt/cross/clang-6009708b43/lib/clang/17/include/arm_neon.h:28:2: sparse: sparse: "NEON intrinsics not available with the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard"
lib/crc/crc64-neon.c: note: in included file:
lib/crc/arm64/crc64-neon.h:3:26: sparse: sparse: Expected ; at end of declaration
lib/crc/arm64/crc64-neon.h:3:26: sparse: sparse: got pmull64
lib/crc/arm64/crc64-neon.h:7:1: sparse: sparse: Expected ; at the end of type declaration
lib/crc/arm64/crc64-neon.h:7:1: sparse: sparse: got }
lib/crc/arm64/crc64-neon.h:12:20: sparse: sparse: Expected ; at end of declaration
lib/crc/arm64/crc64-neon.h:12:20: sparse: sparse: got m
>> lib/crc/arm64/crc64-neon.h:14:9: sparse: sparse: Trying to use reserved word 'return' as identifier
lib/crc/arm64/crc64-neon.h:14:16: sparse: sparse: Expected ; at end of declaration
lib/crc/arm64/crc64-neon.h:14:16: sparse: sparse: got vreinterpretq_u64_p128
lib/crc/arm64/crc64-neon.h:15:1: sparse: sparse: Expected ; at the end of type declaration
lib/crc/arm64/crc64-neon.h:15:1: sparse: sparse: got }
lib/crc/arm64/crc64-neon.h:21:1: sparse: sparse: Expected ; at the end of type declaration
lib/crc/arm64/crc64-neon.h:21:1: sparse: sparse: got }
lib/crc/crc64-neon.c:22:20: sparse: sparse: Expected ; at end of statement
lib/crc/crc64-neon.c:22:20: sparse: sparse: got fold_consts
lib/crc/crc64-neon.c:23:20: sparse: sparse: Expected ; at end of statement
lib/crc/crc64-neon.c:23:20: sparse: sparse: got v0
lib/crc/crc64-neon.c:24:20: sparse: sparse: Expected ; at end of statement
lib/crc/crc64-neon.c:24:20: sparse: sparse: got zero
lib/crc/crc64-neon.c:41:20: sparse: sparse: Expected ; at end of statement
lib/crc/crc64-neon.c:41:20: sparse: sparse: got bconsts
lib/crc/crc64-neon.c:42:20: sparse: sparse: Expected ; at end of statement
lib/crc/crc64-neon.c:42:20: sparse: sparse: got final
lib/crc/crc64-neon.c:27:17: sparse: sparse: undefined identifier 'v0'
lib/crc/crc64-neon.c:27:23: sparse: sparse: undefined identifier 'vreinterpretq_u64_u8'
lib/crc/crc64-neon.c:34:17: sparse: sparse: undefined identifier 'v0'
lib/crc/crc64-neon.c:34:22: sparse: sparse: undefined identifier 'pmull64'
lib/crc/crc64-neon.c:34:49: sparse: sparse: undefined identifier 'pmull64_high'
lib/crc/crc64-neon.c:38:9: sparse: sparse: undefined identifier 'v0'
lib/crc/crc64-neon.c:38:14: sparse: sparse: undefined identifier 'vextq_u64'
lib/crc/crc64-neon.c:38:39: sparse: sparse: undefined identifier 'pmull64_hi_lo'
lib/crc/crc64-neon.c:44:9: sparse: sparse: undefined identifier 'v0'
lib/crc/crc64-neon.c:44:15: sparse: sparse: undefined identifier 'vextq_u64'
lib/crc/crc64-neon.c:44:43: sparse: sparse: undefined identifier 'pmull64_hi_lo'
lib/crc/crc64-neon.c:46:16: sparse: sparse: undefined identifier 'vgetq_lane_u64'
vim +/return +14 lib/crc/arm64/crc64-neon.h
061cef5fcee5a4 Ard Biesheuvel 2026-04-22 8
061cef5fcee5a4 Ard Biesheuvel 2026-04-22 9 static inline uint64x2_t pmull64_high(uint64x2_t a, uint64x2_t b)
061cef5fcee5a4 Ard Biesheuvel 2026-04-22 10 {
061cef5fcee5a4 Ard Biesheuvel 2026-04-22 11 poly64x2_t l = vreinterpretq_p64_u64(a);
061cef5fcee5a4 Ard Biesheuvel 2026-04-22 12 poly64x2_t m = vreinterpretq_p64_u64(b);
061cef5fcee5a4 Ard Biesheuvel 2026-04-22 13
061cef5fcee5a4 Ard Biesheuvel 2026-04-22 @14 return vreinterpretq_u64_p128(vmull_high_p64(l, m));
061cef5fcee5a4 Ard Biesheuvel 2026-04-22 15 }
061cef5fcee5a4 Ard Biesheuvel 2026-04-22 16
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-07-08 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 20:01 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-13 21:04 lib/crc/arm64/crc64-neon.h:14:9: sparse: sparse: Trying to use reserved word 'return' as identifier 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=202607090311.fsN30k2z-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.