All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/2] lib/xor: make xor prototypes more friendely to compiler vectorization
Date: Fri, 28 Jan 2022 01:14:44 +0800	[thread overview]
Message-ID: <202201280125.Q4T02G9Q-lkp@intel.com> (raw)
In-Reply-To: <20220127081227.2430-2-ardb@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 5093 bytes --]

Hi Ard,

I love your patch! Yet something to improve:

[auto build test ERROR on e783362eb54cd99b2cac8b3a9aeac942e6f6ac07]

url:    https://github.com/0day-ci/linux/commits/Ard-Biesheuvel/xor-enable-auto-vectorization-in-Clang/20220127-161449
base:   e783362eb54cd99b2cac8b3a9aeac942e6f6ac07
config: arm64-randconfig-r015-20220127 (https://download.01.org/0day-ci/archive/20220128/202201280125.Q4T02G9Q-lkp(a)intel.com/config)
compiler: aarch64-linux-gcc (GCC) 11.2.0
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/0day-ci/linux/commit/543912d52a64185845fd9bde2412680ef0156a7c
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Ard-Biesheuvel/xor-enable-auto-vectorization-in-Clang/20220127-161449
        git checkout 543912d52a64185845fd9bde2412680ef0156a7c
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm64 SHELL=/bin/bash

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

All errors (new ones prefixed by >>):

   arch/arm64/lib/xor-neon.c:13:6: warning: no previous prototype for 'xor_arm64_neon_2' [-Wmissing-prototypes]
      13 | void xor_arm64_neon_2(unsigned long bytes, unsigned long * __restrict p1,
         |      ^~~~~~~~~~~~~~~~
   arch/arm64/lib/xor-neon.c:40:6: warning: no previous prototype for 'xor_arm64_neon_3' [-Wmissing-prototypes]
      40 | void xor_arm64_neon_3(unsigned long bytes, unsigned long * __restrict p1,
         |      ^~~~~~~~~~~~~~~~
   arch/arm64/lib/xor-neon.c:76:6: warning: no previous prototype for 'xor_arm64_neon_4' [-Wmissing-prototypes]
      76 | void xor_arm64_neon_4(unsigned long bytes, unsigned long * __restrict p1,
         |      ^~~~~~~~~~~~~~~~
   arch/arm64/lib/xor-neon.c:121:6: warning: no previous prototype for 'xor_arm64_neon_5' [-Wmissing-prototypes]
     121 | void xor_arm64_neon_5(unsigned long bytes, unsigned long * __restrict p1,
         |      ^~~~~~~~~~~~~~~~
   arch/arm64/lib/xor-neon.c: In function 'xor_neon_init':
>> arch/arm64/lib/xor-neon.c:316:43: error: assignment to 'void (*)(long unsigned int,  long unsigned int * __restrict__,  const long unsigned int * __restrict__,  const long unsigned int * __restrict__)' from incompatible pointer type 'void (*)(long unsigned int,  long unsigned int *, long unsigned int *, long unsigned int *)' [-Werror=incompatible-pointer-types]
     316 |                 xor_block_inner_neon.do_3 = xor_arm64_eor3_3;
         |                                           ^
>> arch/arm64/lib/xor-neon.c:317:43: error: assignment to 'void (*)(long unsigned int,  long unsigned int * __restrict__,  const long unsigned int * __restrict__,  const long unsigned int * __restrict__,  const long unsigned int * __restrict__)' from incompatible pointer type 'void (*)(long unsigned int,  long unsigned int *, long unsigned int *, long unsigned int *, long unsigned int *)' [-Werror=incompatible-pointer-types]
     317 |                 xor_block_inner_neon.do_4 = xor_arm64_eor3_4;
         |                                           ^
   arch/arm64/lib/xor-neon.c:318:43: error: assignment to 'void (*)(long unsigned int,  long unsigned int * __restrict__,  const long unsigned int * __restrict__,  const long unsigned int * __restrict__,  const long unsigned int * __restrict__,  const long unsigned int * __restrict__)' from incompatible pointer type 'void (*)(long unsigned int,  long unsigned int *, long unsigned int *, long unsigned int *, long unsigned int *, long unsigned int *)' [-Werror=incompatible-pointer-types]
     318 |                 xor_block_inner_neon.do_5 = xor_arm64_eor3_5;
         |                                           ^
   cc1: some warnings being treated as errors


vim +316 arch/arm64/lib/xor-neon.c

2c54b423cf85ba Ard Biesheuvel 2021-12-13  312  
2c54b423cf85ba Ard Biesheuvel 2021-12-13  313  static int __init xor_neon_init(void)
2c54b423cf85ba Ard Biesheuvel 2021-12-13  314  {
2c54b423cf85ba Ard Biesheuvel 2021-12-13  315  	if (IS_ENABLED(CONFIG_AS_HAS_SHA3) && cpu_have_named_feature(SHA3)) {
2c54b423cf85ba Ard Biesheuvel 2021-12-13 @316  		xor_block_inner_neon.do_3 = xor_arm64_eor3_3;
2c54b423cf85ba Ard Biesheuvel 2021-12-13 @317  		xor_block_inner_neon.do_4 = xor_arm64_eor3_4;
2c54b423cf85ba Ard Biesheuvel 2021-12-13  318  		xor_block_inner_neon.do_5 = xor_arm64_eor3_5;
2c54b423cf85ba Ard Biesheuvel 2021-12-13  319  	}
2c54b423cf85ba Ard Biesheuvel 2021-12-13  320  	return 0;
2c54b423cf85ba Ard Biesheuvel 2021-12-13  321  }
2c54b423cf85ba Ard Biesheuvel 2021-12-13  322  module_init(xor_neon_init);
2c54b423cf85ba Ard Biesheuvel 2021-12-13  323  

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

  reply	other threads:[~2022-01-27 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  8:12 [PATCH 0/2] xor: enable auto-vectorization in Clang Ard Biesheuvel
2022-01-27  8:12 ` [PATCH 1/2] lib/xor: make xor prototypes more friendely to compiler vectorization Ard Biesheuvel
2022-01-27 17:14   ` kernel test robot [this message]
2022-02-05  4:26   ` Herbert Xu
2022-01-27  8:12 ` [PATCH 2/2] crypto: arm/xor - make vectorized C code Clang-friendly Ard Biesheuvel
2022-01-27 21:36 ` [PATCH 0/2] xor: enable auto-vectorization in Clang Nathan Chancellor

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=202201280125.Q4T02G9Q-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /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.