From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 2/2] selftests/fpu: Add an FPU selftest
Date: Sat, 20 Jun 2020 18:22:18 +0800 [thread overview]
Message-ID: <202006201846.dFC7Iiqw%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2809 bytes --]
In-Reply-To: <20200619174127.22304-3-bp@alien8.de>
References: <20200619174127.22304-3-bp@alien8.de>
TO: Borislav Petkov <bp@alien8.de>
TO: X86 ML <x86@kernel.org>
CC: jpa(a)kernelbug.mail.kapsi.fi
CC: Dave Hansen <dave.hansen@intel.com>
CC: LKML <linux-kernel@vger.kernel.org>
Hi Borislav,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on kselftest/next]
[also build test ERROR on tip/auto-latest linus/master v5.8-rc1 next-20200618]
[cannot apply to tip/x86/core]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Borislav-Petkov/x86-FPU-FPU-sanitization-for-in-kernel-use/20200620-014453
base: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next
config: x86_64-allyesconfig (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 487ca07fcc75d52755c9fe2ee05bcb3b6eeeec44)
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
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
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 >>):
>> ld.lld: error: undefined symbol: __adddf3
>>> referenced by test_fpu.c
>>> test_fpu.o:(test_fpu_get) in archive lib/built-in.a
>>> referenced by test_fpu.c
>>> test_fpu.o:(test_fpu_get) in archive lib/built-in.a
>>> referenced by test_fpu.c
>>> test_fpu.o:(test_fpu_get) in archive lib/built-in.a
--
>> ld.lld: error: undefined symbol: __muldf3
>>> referenced by test_fpu.c
>>> test_fpu.o:(test_fpu_get) in archive lib/built-in.a
>>> referenced by test_fpu.c
>>> test_fpu.o:(test_fpu_get) in archive lib/built-in.a
--
>> ld.lld: error: undefined symbol: __divdf3
>>> referenced by test_fpu.c
>>> test_fpu.o:(test_fpu_get) in archive lib/built-in.a
--
>> ld.lld: error: undefined symbol: __gtdf2
>>> referenced by test_fpu.c
>>> test_fpu.o:(test_fpu_get) in archive lib/built-in.a
>>> referenced by test_fpu.c
>>> test_fpu.o:(test_fpu_get) in archive lib/built-in.a
>>> referenced by test_fpu.c
>>> test_fpu.o:(test_fpu_get) in archive lib/built-in.a
---
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: 75296 bytes --]
next reply other threads:[~2020-06-20 10:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 10:22 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-19 17:41 [PATCH 0/2] x86/FPU: FPU sanitization for in-kernel use Borislav Petkov
2020-06-19 17:41 ` [PATCH 2/2] selftests/fpu: Add an FPU selftest Borislav Petkov
2020-06-19 18:00 ` Andy Lutomirski
2020-06-22 17:12 ` Borislav Petkov
2020-06-22 18:26 ` Andy Lutomirski
2020-06-22 19:01 ` Borislav Petkov
[not found] ` <B4D00859-000A-4F8C-8CFB-45B9BBCCA16D@amacapital.net>
2020-06-23 10:28 ` Borislav Petkov
2020-06-23 18:22 ` Andy Lutomirski
2020-06-23 18:47 ` Borislav Petkov
2020-06-23 19:07 ` Nick Desaulniers
2020-06-23 19:13 ` Borislav Petkov
2020-06-23 20:58 ` Nick Desaulniers
2020-06-23 21:32 ` Borislav Petkov
2020-06-20 19:55 ` kernel test robot
2020-06-20 19:55 ` kernel test robot
2020-06-22 17:04 ` Borislav Petkov
2020-06-22 17:04 ` Borislav Petkov
2020-06-22 18:15 ` Nick Desaulniers
2020-06-22 18:15 ` Nick Desaulniers
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=202006201846.dFC7Iiqw%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.