From: kbuild test robot <fengguang.wu@intel.com>
To: unlisted-recipients:; (no To-header on input)
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@imgtec.com>
Subject: mipsel-linux-gnu-gcc: error: unrecognized command line option '-mcompact-branches=optimal'
Date: Wed, 20 Apr 2016 13:44:28 +0800 [thread overview]
Message-ID: <201604201320.YHjfc2dZ%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
Hi,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 12566cc35d0e68308bde7aad615743d560cb097b
commit: c1a0e9bc885d46e519fd87d35af6a7937abfb986 MIPS: Allow compact branch policy to be changed
date: 6 months ago
config: mips-malta_qemu_32r6_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 c1a0e9bc885d46e519fd87d35af6a7937abfb986
# save the attached .config to linux build tree
make.cross ARCH=mips
All errors (new ones prefixed by >>):
>> mipsel-linux-gnu-gcc: error: unrecognized command line option '-mcompact-branches=optimal'
>> mipsel-linux-gnu-gcc: error: unrecognized command line option '-mcompact-branches=optimal'
make[2]: *** [kernel/bounds.s] Error 1
make[2]: Target '__build' not remade because of errors.
make[1]: *** [prepare0] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [sub-make] Error 2
---
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: 13362 bytes --]
next reply other threads:[~2016-04-20 5:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 5:44 kbuild test robot [this message]
2016-04-20 13:30 ` mipsel-linux-gnu-gcc: error: unrecognized command line option '-mcompact-branches=optimal' Ralf Baechle
2016-04-21 4:51 ` [kbuild-all] " Fengguang Wu
2016-04-21 19:55 ` Maciej W. Rozycki
2016-04-21 20:34 ` Ralf Baechle
2016-04-21 21:10 ` Maciej W. Rozycki
2016-04-22 8:54 ` Paul Burton
2016-04-22 15:48 ` Maciej W. Rozycki
2016-04-21 20:31 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2016-09-12 4:03 kbuild test robot
2016-09-03 23:37 kbuild test robot
2016-08-22 18:37 kbuild test robot
2016-08-16 2:41 kbuild test robot
2016-08-07 13:13 kbuild test robot
2016-07-31 12:43 kbuild test robot
2016-07-22 12:29 kbuild test robot
2016-04-03 13:15 kbuild test robot
2016-03-20 0:43 kbuild test robot
2016-03-14 10:55 kbuild test robot
2016-03-06 15:26 kbuild test robot
2016-02-28 6:47 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=201604201320.YHjfc2dZ%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.burton@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 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.