From: kbuild test robot <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: core.c:undefined reference to `fpu_save'
Date: Mon, 5 Dec 2016 07:43:24 +0800 [thread overview]
Message-ID: <201612050716.KZZrfhUT%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
Hi Andrew,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3e5de27e940d00d8d504dfb96625fb654f641509
commit: c60f169202c7643991a8b4bfeea60e06843d5b5a arch/mn10300/kernel/fpu-nofpu.c: needs asm/elf.h
date: 9 months ago
config: mn10300-allnoconfig (attached as .config)
compiler: am33_2.0-linux-gcc (GCC) 6.2.0
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout c60f169202c7643991a8b4bfeea60e06843d5b5a
# save the attached .config to linux build tree
make.cross ARCH=mn10300
All errors (new ones prefixed by >>):
kernel/built-in.o: In function `.L410':
>> core.c:(.sched.text+0x28a): undefined reference to `fpu_save'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 4367 bytes --]
next reply other threads:[~2016-12-04 23:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 23:43 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-22 3:47 core.c:undefined reference to `fpu_save' kbuild test robot
2017-01-15 2:25 kbuild test robot
2017-01-01 1:50 kbuild test robot
2016-12-25 5:24 kbuild test robot
2016-12-10 17:51 kbuild test robot
2016-11-20 13:50 kbuild test robot
2016-11-13 6:15 kbuild test robot
2016-11-05 23:19 kbuild test robot
2016-10-30 19:39 kbuild test robot
2016-10-16 14:08 kbuild test robot
2016-09-22 2:51 kbuild test robot
2016-09-04 3:23 kbuild test robot
2016-08-28 12:54 kbuild test robot
2016-08-14 13:57 kbuild test robot
2016-08-06 18:29 kbuild test robot
2016-07-31 13:39 kbuild test robot
2016-07-24 3:09 kbuild test robot
2016-07-17 2:25 kbuild test robot
2016-07-03 11:17 kbuild test robot
2016-06-26 13:09 kbuild test robot
2016-06-13 1:56 kbuild test robot
2016-04-19 10:20 kbuild test robot
2016-04-03 7:26 kbuild test robot
2016-03-20 17:49 kbuild test robot
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=201612050716.KZZrfhUT%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).