From: kbuild test robot <fengguang.wu@intel.com>
To: Alex Smith <alex.smith@imgtec.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Ralf Baechle <ralf@linux-mips.org>,
Markos Chandras <markos.chandras@imgtec.com>
Subject: arch/mips/vdso/elf.S:1:0: error: '-march=r3900' requires '-mfp32'
Date: Sun, 16 Oct 2016 10:33:01 +0800 [thread overview]
Message-ID: <201610161054.tAB5MuWr%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
Hi Alex,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 1001354ca34179f3db924eb66672442a173147dc
commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation of a VDSO
date: 11 months ago
config: mips-jmr3927_defconfig (attached as .config)
compiler: mips-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
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 ebb5e78cc63417a35254a791de66e1cc84f963cc
# save the attached .config to linux build tree
make.cross ARCH=mips
All errors (new ones prefixed by >>):
>> arch/mips/vdso/elf.S:1:0: error: '-march=r3900' requires '-mfp32'
/*
--
>> arch/mips/vdso/sigreturn.S:1:0: error: '-march=r3900' requires '-mfp32'
/*
vim +1 arch/mips/vdso/elf.S
> 1 /*
2 * Copyright (C) 2015 Imagination Technologies
3 * Author: Alex Smith <alex.smith@imgtec.com>
4 *
---
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: 10118 bytes --]
next reply other threads:[~2016-10-16 2:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 2:33 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-11 23:53 kbuild test robot
2017-02-05 14:54 kbuild test robot
2017-01-15 0:56 kbuild test robot
2016-12-11 1:04 kbuild test robot
2016-12-13 4:02 ` Ralf Baechle
2016-12-16 0:57 ` Maciej W. Rozycki
2016-11-13 1:34 kbuild test robot
2016-11-05 23:28 kbuild test robot
2016-10-02 2:12 kbuild test robot
2016-09-23 1:46 kbuild test robot
2016-09-14 15:51 kbuild test robot
2016-09-03 23:29 kbuild test robot
2016-08-28 11:12 kbuild test robot
2016-08-01 20:15 kbuild test robot
2016-07-22 17:03 kbuild test robot
2016-04-17 6:25 kbuild test robot
2016-04-03 9:13 kbuild test robot
2016-03-20 1:38 kbuild test robot
2016-03-13 9:08 kbuild test robot
2016-03-06 6:39 kbuild test robot
2016-02-28 8:17 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=201610161054.tAB5MuWr%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=alex.smith@imgtec.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markos.chandras@imgtec.com \
--cc=ralf@linux-mips.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
Powered by JetHome