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,
Chris Zankel <chris@zankel.net>,
Max Filippov <jcmvbkbc@gmail.com>
Subject: arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'rur.ae_ovf_sar'
Date: Tue, 19 Apr 2016 21:41:29 +0800 [thread overview]
Message-ID: <201604192125.3RXEKl3t%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4058 bytes --]
Hi,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 12566cc35d0e68308bde7aad615743d560cb097b
commit: 9da8320bb97768e35f2e64fa7642015271d672eb xtensa: add test_kc705_hifi variant
date: 5 weeks ago
config: xtensa-audio_kc705_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 9da8320bb97768e35f2e64fa7642015271d672eb
# save the attached .config to linux build tree
make.cross ARCH=xtensa
All errors (new ones prefixed by >>):
arch/xtensa/kernel/coprocessor.S: Assembler messages:
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'rur.ae_ovf_sar'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'rur.ae_bithead'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'rur.ae_ts_fts_bu_bp'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'rur.ae_cw_sd_no'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'rur.ae_cbegin0'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'rur.ae_cend0'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i'
>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i'
vim +93 arch/xtensa/kernel/coprocessor.S
c658eac6 Chris Zankel 2008-02-12 87 .else; \
c658eac6 Chris Zankel 2008-02-12 88 .long 0; \
c658eac6 Chris Zankel 2008-02-12 89 .endif; \
c658eac6 Chris Zankel 2008-02-12 90 .long THREAD_XTREGS_CP##x
5a0015d6 Chris Zankel 2005-06-23 91
c658eac6 Chris Zankel 2008-02-12 92 SAVE_CP_REGS(0)
c658eac6 Chris Zankel 2008-02-12 @93 SAVE_CP_REGS(1)
c658eac6 Chris Zankel 2008-02-12 94 SAVE_CP_REGS(2)
c658eac6 Chris Zankel 2008-02-12 95 SAVE_CP_REGS(3)
c658eac6 Chris Zankel 2008-02-12 96 SAVE_CP_REGS(4)
c658eac6 Chris Zankel 2008-02-12 97 SAVE_CP_REGS(5)
c658eac6 Chris Zankel 2008-02-12 98 SAVE_CP_REGS(6)
c658eac6 Chris Zankel 2008-02-12 99 SAVE_CP_REGS(7)
5a0015d6 Chris Zankel 2005-06-23 100
c658eac6 Chris Zankel 2008-02-12 101 LOAD_CP_REGS(0)
c658eac6 Chris Zankel 2008-02-12 @102 LOAD_CP_REGS(1)
c658eac6 Chris Zankel 2008-02-12 103 LOAD_CP_REGS(2)
c658eac6 Chris Zankel 2008-02-12 104 LOAD_CP_REGS(3)
c658eac6 Chris Zankel 2008-02-12 105 LOAD_CP_REGS(4)
:::::: The code at line 93 was first introduced by commit
:::::: c658eac628aa8df040dfe614556d95e6da3a9ffb [XTENSA] Add support for configurable registers and coprocessors
:::::: TO: Chris Zankel <chris@zankel.net>
:::::: CC: Chris Zankel <chris@zankel.net>
---
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: 11868 bytes --]
next reply other threads:[~2016-04-19 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 13:41 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-02 23:52 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=201604192125.3RXEKl3t%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=chris@zankel.net \
--cc=jcmvbkbc@gmail.com \
--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®