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}:508: Error: unknown opcode
Date: Sun, 13 Nov 2016 08:25:58 +0800 [thread overview]
Message-ID: <201611130855.L90CTyIL%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3244 bytes --]
Hi Rich,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: b4214e41b7152b1964a3421a40251d202ae2d2c0 sh: add SMP support for J2
date: 3 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}:508: Error: unknown opcode
{standard input}:573: Error: unknown opcode
{standard input}:1324: Error: unknown opcode
{standard input}:1463: Error: unknown opcode
{standard input}:1490: Error: unknown opcode
{standard input}:2152: Error: unknown opcode
{standard input}:2169: Error: unknown opcode
{standard input}:3888: Error: unknown opcode
{standard input}:3917: Error: unknown opcode
{standard input}:4232: Error: unknown opcode
--
{standard input}: Assembler messages:
{standard input}:211: Error: unknown opcode
{standard input}:232: Error: unknown opcode
{standard input}:261: Error: unknown opcode
{standard input}:275: Error: unknown opcode
{standard input}:300: Error: unknown opcode
{standard input}:313: Error: unknown opcode
{standard input}:487: Error: unknown opcode
>> {standard input}:508: Error: unknown opcode
{standard input}:537: Error: unknown opcode
{standard input}:551: Error: unknown opcode
{standard input}:576: Error: unknown opcode
{standard input}:589: Error: unknown opcode
{standard input}:2230: Error: unknown opcode
{standard input}:2403: Error: unknown opcode
{standard input}:2435: Error: unknown opcode
--
{standard input}: Assembler messages:
{standard input}:360: Error: unknown opcode
{standard input}:427: Error: unknown opcode
{standard input}:454: Error: unknown opcode
{standard input}:469: Error: unknown opcode
{standard input}:482: Error: unknown opcode
{standard input}:495: Error: unknown opcode
>> {standard input}:508: Error: unknown opcode
{standard input}:521: Error: unknown opcode
{standard input}:616: Error: unknown opcode
{standard input}:660: Error: unknown opcode
{standard input}:691: Error: unknown opcode
{standard input}:722: Error: unknown opcode
{standard input}:753: Error: unknown opcode
{standard input}:784: Error: unknown opcode
{standard input}:815: Error: unknown opcode
{standard input}:845: Error: unknown opcode
{standard input}:914: Error: unknown opcode
{standard input}:944: Error: unknown opcode
{standard input}:959: Error: unknown opcode
{standard input}:972: Error: unknown opcode
{standard input}:1000: Error: unknown opcode
{standard input}:1060: 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: 11431 bytes --]
next reply other threads:[~2016-11-13 0:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 0:25 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-02 7:20 {standard input}:508: Error: unknown opcode 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=201611130855.L90CTyIL%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).