From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [rcu:dev.2020.08.10a 105/111] riscv64-linux-ld: main.c:undefined reference to `rcu_read_unlock_strict'
Date: Wed, 12 Aug 2020 07:40:03 +0800 [thread overview]
Message-ID: <202008120701.iIY4BdGm%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2020.08.10a
head: 9dd4d242c535c30266a08806314ea6b016f94617
commit: 9e20110f8ef2745df8f4fe2d679114dccfaaa1af [105/111] rcu: Report QS for outermost PREEMPT=n rcu_read_unlock() for strict GPs
config: riscv-allnoconfig (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
git checkout 9e20110f8ef2745df8f4fe2d679114dccfaaa1af
# 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 >>):
riscv64-linux-ld: init/main.o: in function `.L0 ':
main.c:(.ref.text+0x34): undefined reference to `rcu_read_unlock_strict'
>> riscv64-linux-ld: main.c:(.ref.text+0x64): undefined reference to `rcu_read_unlock_strict'
riscv64-linux-ld: kernel/fork.o: in function `.L26':
fork.c:(.text+0x144): undefined reference to `rcu_read_unlock_strict'
riscv64-linux-ld: kernel/fork.o: in function `.L27':
fork.c:(.text+0x164): undefined reference to `rcu_read_unlock_strict'
riscv64-linux-ld: kernel/fork.o: in function `.L183':
fork.c:(.text+0xbb4): undefined reference to `rcu_read_unlock_strict'
riscv64-linux-ld: kernel/fork.o:fork.c:(.text+0xbd4): more undefined references to `rcu_read_unlock_strict' follow
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 5373 bytes --]
reply other threads:[~2020-08-11 23:40 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=202008120701.iIY4BdGm%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.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 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®