mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Alexander Lobakin <alexandr.lobakin@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org, Yury Norov <yury.norov@gmail.com>
Subject: [alobakin:bitops 3/6] include/linux/bitops.h:42:1: error: use of undeclared identifier 'arch___set_bit'
Date: Tue, 14 Jun 2022 04:22:17 +0800	[thread overview]
Message-ID: <202206140447.OqHwRDRY-lkp@intel.com> (raw)

tree:   https://github.com/alobakin/linux bitops
head:   d8371d0e4328c4cb6fa25350bd5132f25b386672
commit: 4f9a98e0945a7cb9130bb04be4b3ecec35e16a81 [3/6] bitops: unify non-atomic bitops prototypes across architectures
config: hexagon-buildonly-randconfig-r001-20220613 (https://download.01.org/0day-ci/archive/20220614/202206140447.OqHwRDRY-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project d378268ead93c85803c270277f0243737b536ae7)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/alobakin/linux/commit/4f9a98e0945a7cb9130bb04be4b3ecec35e16a81
        git remote add alobakin https://github.com/alobakin/linux
        git fetch --no-tags alobakin bitops
        git checkout 4f9a98e0945a7cb9130bb04be4b3ecec35e16a81
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon prepare

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   In file included from kernel/bounds.c:13:
   In file included from include/linux/log2.h:12:
>> include/linux/bitops.h:42:1: error: use of undeclared identifier 'arch___set_bit'
   __check_bitop_pr(__set_bit);
   ^
   include/linux/bitops.h:39:28: note: expanded from macro '__check_bitop_pr'
           static_assert(__same_type(arch_##name, generic_##name) &&       \
                                     ^
   <scratch space>:111:1: note: expanded from here
   arch___set_bit
   ^
   In file included from kernel/bounds.c:13:
   In file included from include/linux/log2.h:12:
>> include/linux/bitops.h:43:1: error: use of undeclared identifier 'arch___clear_bit'; did you mean '__clear_bit'?
   __check_bitop_pr(__clear_bit);
   ^
   include/linux/bitops.h:39:28: note: expanded from macro '__check_bitop_pr'
           static_assert(__same_type(arch_##name, generic_##name) &&       \
                                     ^
   <scratch space>:115:1: note: expanded from here
   arch___clear_bit
   ^
   arch/hexagon/include/asm/bitops.h:131:1: note: '__clear_bit' declared here
   __clear_bit(unsigned long nr, volatile unsigned long *addr)
   ^
   In file included from kernel/bounds.c:13:
   In file included from include/linux/log2.h:12:
>> include/linux/bitops.h:44:1: error: use of undeclared identifier 'arch___change_bit'; did you mean '__change_bit'?
   __check_bitop_pr(__change_bit);
   ^
   include/linux/bitops.h:39:28: note: expanded from macro '__check_bitop_pr'
           static_assert(__same_type(arch_##name, generic_##name) &&       \
                                     ^
   <scratch space>:119:1: note: expanded from here
   arch___change_bit
   ^
   arch/hexagon/include/asm/bitops.h:143:1: note: '__change_bit' declared here
   __change_bit(unsigned long nr, volatile unsigned long *addr)
   ^
   In file included from kernel/bounds.c:13:
   In file included from include/linux/log2.h:12:
>> include/linux/bitops.h:45:1: error: use of undeclared identifier 'arch___test_and_set_bit'; did you mean '__test_and_set_bit'?
   __check_bitop_pr(__test_and_set_bit);
   ^
   include/linux/bitops.h:39:28: note: expanded from macro '__check_bitop_pr'
           static_assert(__same_type(arch_##name, generic_##name) &&       \
                                     ^
   <scratch space>:123:1: note: expanded from here
   arch___test_and_set_bit
   ^
   arch/hexagon/include/asm/bitops.h:156:1: note: '__test_and_set_bit' declared here
   __test_and_set_bit(unsigned long nr, volatile unsigned long *addr)
   ^
   In file included from kernel/bounds.c:13:
   In file included from include/linux/log2.h:12:
>> include/linux/bitops.h:46:1: error: use of undeclared identifier 'arch___test_and_clear_bit'; did you mean '__test_and_clear_bit'?
   __check_bitop_pr(__test_and_clear_bit);
   ^
   include/linux/bitops.h:39:28: note: expanded from macro '__check_bitop_pr'
           static_assert(__same_type(arch_##name, generic_##name) &&       \
                                     ^
   <scratch space>:127:1: note: expanded from here
   arch___test_and_clear_bit
   ^
   arch/hexagon/include/asm/bitops.h:150:1: note: '__test_and_clear_bit' declared here
   __test_and_clear_bit(unsigned long nr, volatile unsigned long *addr)
   ^
   In file included from kernel/bounds.c:13:
   In file included from include/linux/log2.h:12:
>> include/linux/bitops.h:47:1: error: use of undeclared identifier 'arch___test_and_change_bit'; did you mean '__test_and_change_bit'?
   __check_bitop_pr(__test_and_change_bit);
   ^
   include/linux/bitops.h:39:28: note: expanded from macro '__check_bitop_pr'
           static_assert(__same_type(arch_##name, generic_##name) &&       \
                                     ^
   <scratch space>:131:1: note: expanded from here
   arch___test_and_change_bit
   ^
   arch/hexagon/include/asm/bitops.h:162:1: note: '__test_and_change_bit' declared here
   __test_and_change_bit(unsigned long nr, volatile unsigned long *addr)
   ^
   In file included from kernel/bounds.c:13:
   In file included from include/linux/log2.h:12:
>> include/linux/bitops.h:48:1: error: use of undeclared identifier 'arch_test_bit'
   __check_bitop_pr(test_bit);
   ^
   include/linux/bitops.h:39:28: note: expanded from macro '__check_bitop_pr'
           static_assert(__same_type(arch_##name, generic_##name) &&       \
                                     ^
   <scratch space>:135:1: note: expanded from here
   arch_test_bit
   ^
   7 errors generated.
   make[2]: *** [scripts/Makefile.build:117: kernel/bounds.s] Error 1
   make[2]: Target '__build' not remade because of errors.
   make[1]: *** [Makefile:1200: prepare0] Error 2
   make[1]: Target 'prepare' not remade because of errors.
   make: *** [Makefile:219: __sub-make] Error 2
   make: Target 'prepare' not remade because of errors.


vim +/arch___set_bit +42 include/linux/bitops.h

    36	
    37	/* Check that the bitops prototypes are sane */
    38	#define __check_bitop_pr(name)						\
    39		static_assert(__same_type(arch_##name, generic_##name) &&	\
    40			      __same_type(name, generic_##name))
    41	
  > 42	__check_bitop_pr(__set_bit);
  > 43	__check_bitop_pr(__clear_bit);
  > 44	__check_bitop_pr(__change_bit);
  > 45	__check_bitop_pr(__test_and_set_bit);
  > 46	__check_bitop_pr(__test_and_clear_bit);
  > 47	__check_bitop_pr(__test_and_change_bit);
  > 48	__check_bitop_pr(test_bit);
    49	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-06-13 20:59 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=202206140447.OqHwRDRY-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alexandr.lobakin@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=yury.norov@gmail.com \
    /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®