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}:854: Error: unknown opcode
Date: Sun, 20 Nov 2016 13:59:32 +0800 [thread overview]
Message-ID: <201611201323.3Rc4Oxv6%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4412 bytes --]
Hi Rich,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 77079b133f242d3e3710c9b89ed54458307e54ff
commit: b4214e41b7152b1964a3421a40251d202ae2d2c0 sh: add SMP support for J2
date: 4 months 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}:854: Error: unknown opcode
{standard input}:1222: Error: unknown opcode
{standard input}:1536: Error: unknown opcode
{standard input}:1619: Error: unknown opcode
{standard input}:1714: Error: unknown opcode
{standard input}:1886: Error: unknown opcode
{standard input}:2084: Error: unknown opcode
{standard input}:2250: Error: unknown opcode
{standard input}:2645: Error: unknown opcode
{standard input}:3047: Error: unknown opcode
{standard input}:3063: Error: unknown opcode
{standard input}:4928: Error: unknown opcode
{standard input}:5686: Error: unknown opcode
{standard input}:6058: Error: unknown opcode
{standard input}:6174: Error: unknown opcode
{standard input}:6186: Error: unknown opcode
{standard input}:6217: Error: unknown opcode
{standard input}:6272: Error: unknown opcode
{standard input}:6308: Error: unknown opcode
{standard input}:6328: Error: unknown opcode
{standard input}:6352: Error: unknown opcode
{standard input}:6446: Error: unknown opcode
{standard input}:6458: Error: unknown opcode
{standard input}:6503: Error: unknown opcode
{standard input}:6536: Error: unknown opcode
{standard input}:6548: Error: unknown opcode
{standard input}:6799: Error: unknown opcode
{standard input}:6858: Error: unknown opcode
{standard input}:7055: Error: unknown opcode
{standard input}:7112: Error: unknown opcode
{standard input}:7187: Error: unknown opcode
{standard input}:7258: Error: unknown opcode
{standard input}:7324: Error: unknown opcode
{standard input}:7384: Error: unknown opcode
{standard input}:7498: Error: unknown opcode
{standard input}:7526: Error: unknown opcode
{standard input}:7801: Error: unknown opcode
{standard input}:7850: Error: unknown opcode
{standard input}:7935: Error: unknown opcode
{standard input}:7947: Error: unknown opcode
{standard input}:8153: Error: unknown opcode
{standard input}:8305: Error: unknown opcode
{standard input}:8465: Error: unknown opcode
{standard input}:9687: Error: unknown opcode
{standard input}:9701: Error: unknown opcode
{standard input}:9719: Error: unknown opcode
{standard input}:9742: Error: unknown opcode
{standard input}:9767: Error: unknown opcode
{standard input}:9868: Error: unknown opcode
{standard input}:10055: Error: unknown opcode
{standard input}:10068: Error: unknown opcode
{standard input}:10329: Error: unknown opcode
{standard input}:10347: Error: unknown opcode
{standard input}:10366: Error: unknown opcode
{standard input}:10549: Error: unknown opcode
{standard input}:10607: Error: unknown opcode
{standard input}:10729: Error: unknown opcode
{standard input}:10830: Error: unknown opcode
{standard input}:11163: Error: unknown opcode
{standard input}:11176: Error: unknown opcode
{standard input}:11244: Error: unknown opcode
{standard input}:11292: Error: unknown opcode
{standard input}:11370: Error: unknown opcode
{standard input}:11418: Error: unknown opcode
{standard input}:11446: Error: unknown opcode
{standard input}:11479: Error: unknown opcode
{standard input}:11901: Error: unknown opcode
{standard input}:12213: Error: unknown opcode
{standard input}:12348: Error: unknown opcode
{standard input}:12632: Error: unknown opcode
{standard input}:12647: Error: unknown opcode
{standard input}:12733: 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 --]
reply other threads:[~2016-11-20 5:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201611201323.3Rc4Oxv6%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
all inboxes | Powered by JetHome®