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=r3000' requires '-mfp32'
Date: Sun, 17 Apr 2016 08:57:14 +0800 [thread overview]
Message-ID: <201604170812.GAklda3M%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
Hi Alex,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 306a63bee192859ebd32c7328c7766636d882d8f
commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation of a VDSO
date: 5 months ago
config: mips-decstation_defconfig (attached as .config)
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=r3000' requires '-mfp32'
/*
^
--
>> arch/mips/vdso/sigreturn.S:1:0: error: '-march=r3000' 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/octet-stream, Size: 9029 bytes --]
next reply other threads:[~2016-04-17 0:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 0:57 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-06 6:15 kbuild test robot
2017-01-22 11:01 kbuild test robot
2017-01-15 13:12 kbuild test robot
2017-01-01 16:45 kbuild test robot
2016-12-25 1:16 kbuild test robot
2016-12-25 12:09 ` Ralf Baechle
2016-12-04 1:59 kbuild test robot
2016-11-20 12:05 kbuild test robot
2016-11-06 3:08 kbuild test robot
2016-10-30 8:22 kbuild test robot
2016-10-23 0:43 kbuild test robot
2016-09-18 0:08 kbuild test robot
2016-09-04 7:38 kbuild test robot
2016-08-22 17:07 kbuild test robot
2016-08-14 6:42 kbuild test robot
2016-08-02 2:07 kbuild test robot
2016-07-22 21:29 kbuild test robot
2016-03-20 18:54 kbuild test robot
2016-03-12 23:38 kbuild test robot
2016-02-29 8:26 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=201604170812.GAklda3M%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
all inboxes | Powered by JetHome®