From: Borislav Petkov <bp@suse.de>
To: kernel test robot <lkp@intel.com>
Cc: Petteri Aimonen <jpa@git.mail.kapsi.fi>,
kbuild-all@lists.01.org,
Nick Desaulniers <ndesaulniers@google.com>,
x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [bp:tip-x86-fpu 2/2] test_fpu.c:undefined reference to `__sanitizer_cov_trace_cmpd'
Date: Sat, 27 Jun 2020 12:22:40 +0200 [thread overview]
Message-ID: <20200627102240.GC18956@zn.tnic> (raw)
In-Reply-To: <202006271139.H8IXpYlR%lkp@intel.com>
On Sat, Jun 27, 2020 at 11:15:42AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tip-x86-fpu
> head: dca364a883e0ac1f61b4d4e482edf66e63ffcdd2
> commit: dca364a883e0ac1f61b4d4e482edf66e63ffcdd2 [2/2] selftests/fpu: Add an FPU selftest
> config: x86_64-allyesconfig (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
>
> 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: lib/test_fpu.o: in function `test_fpu_get':
> >> test_fpu.c:(.text+0x16e): undefined reference to `__sanitizer_cov_trace_cmpd'
> >> ld: test_fpu.c:(.text+0x1a7): undefined reference to `__sanitizer_cov_trace_cmpd'
> ld: test_fpu.c:(.text+0x1e0): undefined reference to `__sanitizer_cov_trace_cmpd'
>
> ---
I'm getting sick'n'tired of having to deal with compilers lately:
---
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index e4add3e89c47..5842885ab184 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -2309,7 +2309,7 @@ config TEST_HMM
config TEST_FPU
tristate "Test floating point operations in kernel space"
- depends on X86
+ depends on X86 && !KCOV_INSTRUMENT_ALL
help
Enable this option to add /sys/kernel/debug/selftest_helpers/test_fpu
which will trigger a sequence of floating point operations. This is used
---
Thx for the report, folded in.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
parent reply other threads:[~2020-06-27 10:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <202006271139.H8IXpYlR%lkp@intel.com>]
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=20200627102240.GC18956@zn.tnic \
--to=bp@suse.de \
--cc=jpa@git.mail.kapsi.fi \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ndesaulniers@google.com \
--cc=x86@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®