From: kbuild test robot <fengguang.wu@intel.com>
To: Rich Felker <dalias@libc.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: {standard input}:199: Error: unknown opcode
Date: Fri, 23 Sep 2016 01:07:00 +0800 [thread overview]
Message-ID: <201609230158.U4N91T9Y%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
Hi Rich,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 7d1e042314619115153a0f6f06e4552c09a50e13
commit: b4214e41b7152b1964a3421a40251d202ae2d2c0 sh: add SMP support for J2
date: 7 weeks ago
config: sh-j2_defconfig (attached as .config)
compiler: sh4-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 b4214e41b7152b1964a3421a40251d202ae2d2c0
# save the attached .config to linux build tree
make.cross ARCH=sh
All errors (new ones prefixed by >>):
{standard input}: Assembler messages:
>> {standard input}:199: Error: unknown opcode
{standard input}:1229: Error: unknown opcode
--
{standard input}: Assembler messages:
{standard input}:162: Error: unknown opcode
>> {standard input}:199: Error: unknown opcode
{standard input}:324: Error: unknown opcode
{standard input}:520: Error: unknown opcode
{standard input}:619: Error: unknown opcode
---
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: 11428 bytes --]
next reply other threads:[~2016-09-22 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 17:07 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-05 23:02 {standard input}:199: Error: unknown opcode kbuild test robot
2017-01-15 1:09 kbuild test robot
2016-12-25 0:26 kbuild test robot
2016-12-04 2:18 kbuild test robot
2016-10-23 3:15 kbuild test robot
2016-09-12 10:00 kbuild test robot
2016-08-29 23:23 kbuild test robot
2016-08-14 8:48 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=201609230158.U4N91T9Y%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=dalias@libc.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).