From: kernel test robot <lkp@intel.com>
To: Atish Patra <atishp@rivosinc.com>
Cc: kbuild-all@lists.01.org, Atish Patra <Atish.Patra@wdc.com>,
linux-kernel@vger.kernel.org
Subject: [atishp04:kvm_perf_rfc 15/24] f_fs.c:undefined reference to `wrong_size_cmpxchg'
Date: Sat, 16 Jul 2022 14:28:39 +0800 [thread overview]
Message-ID: <202207161421.rzT6feio-lkp@intel.com> (raw)
tree: https://github.com/atishp04/linux kvm_perf_rfc
head: 84a3fd7f92957f64c411595a9efcc2eed18db2be
commit: 5faed77192c5455fe17fb4e6aea87e5bcc48a13d [15/24] COVER
config: nios2-randconfig-r005-20220715 (https://download.01.org/0day-ci/archive/20220716/202207161421.rzT6feio-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 12.1.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/atishp04/linux/commit/5faed77192c5455fe17fb4e6aea87e5bcc48a13d
git remote add atishp04 https://github.com/atishp04/linux
git fetch --no-tags atishp04 kvm_perf_rfc
git checkout 5faed77192c5455fe17fb4e6aea87e5bcc48a13d
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=nios2 SHELL=/bin/bash
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 >>):
nios2-linux-ld: drivers/usb/gadget/function/f_fs.o: in function `__generic_cmpxchg_local':
>> f_fs.c:(.text+0x37d0): undefined reference to `wrong_size_cmpxchg'
f_fs.c:(.text+0x37d0): relocation truncated to fit: R_NIOS2_CALL26 against `wrong_size_cmpxchg'
>> nios2-linux-ld: f_fs.c:(.text+0x3804): undefined reference to `wrong_size_cmpxchg'
f_fs.c:(.text+0x3804): relocation truncated to fit: R_NIOS2_CALL26 against `wrong_size_cmpxchg'
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-16 6:30 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=202207161421.rzT6feio-lkp@intel.com \
--to=lkp@intel.com \
--cc=Atish.Patra@wdc.com \
--cc=atishp@rivosinc.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.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®