From: kbuild test robot <lkp@intel.com>
To: Julien Grall <julien.grall@arm.com>
Cc: kbuild-all@lists.01.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Sasha Levin <alexander.levin@microsoft.com>
Subject: [linux-stable-rc:linux-5.4.y 1325/3645] lib/ubsan.c:88: undefined reference to `__ashlti3'
Date: Tue, 10 Mar 2020 17:01:48 +0800 [thread overview]
Message-ID: <202003101744.gbdfbmyS%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2518 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.4.y
head: 6201d69ba49e810a10a557a4f41fd95c55a61983
commit: 735e7a12a639c6c196ac1acf41f024f84281e491 [1325/3645] lib/ubsan: don't serialize UBSAN report
config: riscv-randconfig-a001-20200309 (attached as .config)
compiler: riscv64-linux-gcc (GCC) 9.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 735e7a12a639c6c196ac1acf41f024f84281e491
# save the attached .config to linux build tree
GCC_VERSION=9.2.0 make.cross ARCH=riscv
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
riscv64-linux-ld: lib/ubsan.o: in function `get_signed_val':
>> lib/ubsan.c:88: undefined reference to `__ashlti3'
>> riscv64-linux-ld: lib/ubsan.c:92: undefined reference to `__ashrti3'
vim +88 lib/ubsan.c
c6d308534aef6c Andrey Ryabinin 2016-01-20 85
f0996bc2978e02 Andrey Ryabinin 2019-05-06 86 static s_max get_signed_val(struct type_descriptor *type, void *val)
c6d308534aef6c Andrey Ryabinin 2016-01-20 87 {
c6d308534aef6c Andrey Ryabinin 2016-01-20 @88 if (is_inline_int(type)) {
c6d308534aef6c Andrey Ryabinin 2016-01-20 89 unsigned extra_bits = sizeof(s_max)*8 - type_bit_width(type);
f0996bc2978e02 Andrey Ryabinin 2019-05-06 90 unsigned long ulong_val = (unsigned long)val;
f0996bc2978e02 Andrey Ryabinin 2019-05-06 91
f0996bc2978e02 Andrey Ryabinin 2019-05-06 @92 return ((s_max)ulong_val) << extra_bits >> extra_bits;
c6d308534aef6c Andrey Ryabinin 2016-01-20 93 }
c6d308534aef6c Andrey Ryabinin 2016-01-20 94
c6d308534aef6c Andrey Ryabinin 2016-01-20 95 if (type_bit_width(type) == 64)
c6d308534aef6c Andrey Ryabinin 2016-01-20 96 return *(s64 *)val;
c6d308534aef6c Andrey Ryabinin 2016-01-20 97
c6d308534aef6c Andrey Ryabinin 2016-01-20 98 return *(s_max *)val;
c6d308534aef6c Andrey Ryabinin 2016-01-20 99 }
c6d308534aef6c Andrey Ryabinin 2016-01-20 100
:::::: The code at line 88 was first introduced by commit
:::::: c6d308534aef6c99904bf5862066360ae067abc4 UBSAN: run-time undefined behavior sanity checker
:::::: TO: Andrey Ryabinin <aryabinin@virtuozzo.com>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
---
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: 26328 bytes --]
reply other threads:[~2020-03-10 9:02 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=202003101744.gbdfbmyS%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=julien.grall@arm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.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