All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [sashal-linux-stable:queue-5.4 44/44] arch/riscv/include/asm/processor.h:68:2: error: implicit declaration of function 'barrier'
Date: Mon, 23 Nov 2020 04:34:23 +0800	[thread overview]
Message-ID: <202011230418.ph10pe82-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git queue-5.4
head:   b2a15cebf1822ff1ce0e390d45202f2231047ee2
commit: b2a15cebf1822ff1ce0e390d45202f2231047ee2 [44/44] compiler.h: fix barrier_data() on clang
config: riscv-allyesconfig (attached as .config)
compiler: riscv64-linux-gcc (GCC) 9.3.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://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git/commit/?id=b2a15cebf1822ff1ce0e390d45202f2231047ee2
        git remote add sashal-linux-stable https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git
        git fetch --no-tags sashal-linux-stable queue-5.4
        git checkout b2a15cebf1822ff1ce0e390d45202f2231047ee2
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv 

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 >>):

   In file included from include/linux/prefetch.h:15,
                    from drivers/net/ethernet/emulex/benet/be_main.c:14:
   arch/riscv/include/asm/processor.h: In function 'cpu_relax':
>> arch/riscv/include/asm/processor.h:68:2: error: implicit declaration of function 'barrier' [-Werror=implicit-function-declaration]
      68 |  barrier();
         |  ^~~~~~~
   cc1: some warnings being treated as errors

vim +/barrier +68 arch/riscv/include/asm/processor.h

7db91e57a0acde1 Palmer Dabbelt 2017-07-10  59  
7db91e57a0acde1 Palmer Dabbelt 2017-07-10  60  
7db91e57a0acde1 Palmer Dabbelt 2017-07-10  61  static inline void cpu_relax(void)
7db91e57a0acde1 Palmer Dabbelt 2017-07-10  62  {
7db91e57a0acde1 Palmer Dabbelt 2017-07-10  63  #ifdef __riscv_muldiv
7db91e57a0acde1 Palmer Dabbelt 2017-07-10  64  	int dummy;
7db91e57a0acde1 Palmer Dabbelt 2017-07-10  65  	/* In lieu of a halt instruction, induce a long-latency stall. */
7db91e57a0acde1 Palmer Dabbelt 2017-07-10  66  	__asm__ __volatile__ ("div %0, %0, zero" : "=r" (dummy));
7db91e57a0acde1 Palmer Dabbelt 2017-07-10  67  #endif
7db91e57a0acde1 Palmer Dabbelt 2017-07-10 @68  	barrier();
7db91e57a0acde1 Palmer Dabbelt 2017-07-10  69  }
7db91e57a0acde1 Palmer Dabbelt 2017-07-10  70  

:::::: The code at line 68 was first introduced by commit
:::::: 7db91e57a0acde126a162ababfb1e0ab190130cb RISC-V: Task implementation

:::::: TO: Palmer Dabbelt <palmer@dabbelt.com>
:::::: CC: Palmer Dabbelt <palmer@dabbelt.com>

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

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 60966 bytes --]

                 reply	other threads:[~2020-11-22 20:34 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=202011230418.ph10pe82-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.