From: Fengguang Wu <fengguang.wu@intel.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Chris Zankel <chris@zankel.net>,
kbuild-all@01.org, LKML <linux-kernel@vger.kernel.org>,
Philip Li <philip.li@intel.com>
Subject: Re: [kbuild-all] arch/xtensa/include/asm/initialize_mmu.h:55: Error: invalid register 'atomctl' for 'wsr' instruction
Date: Tue, 26 Jul 2016 12:42:57 +0800 [thread overview]
Message-ID: <20160726044257.GA29614@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <CAMo8Bf+nZwLx2H36-zHu5+OUzMv5GqWkdmEFS3TrJampWq4ptg@mail.gmail.com>
Hi Max,
On Tue, Jul 26, 2016 at 02:20:25AM +0300, Max Filippov wrote:
>Hi Fengguang,
>
>On Fri, Jul 22, 2016 at 3:44 PM, Fengguang Wu <fengguang.wu@intel.com> wrote:
>> On Fri, Jul 22, 2016 at 06:32:28PM +0800, kbuild test robot wrote:
>>> FYI, the error/warning still remains.
>>>
>>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>> master
>>> head: 47ef4ad2684d380dd6d596140fb79395115c3950
>>> commit: 9da8320bb97768e35f2e64fa7642015271d672eb xtensa: add
>>> test_kc705_hifi variant
>>> date: 4 months ago
>>> config: xtensa-audio_kc705_defconfig (attached as .config)
>>> compiler: xtensa-linux-gcc (GCC) 4.9.0
>>
>>> All errors (new ones prefixed by >>):
>>>
>>> arch/xtensa/include/asm/initialize_mmu.h: Assembler messages:
>>>>>
>>>>> arch/xtensa/include/asm/initialize_mmu.h:55: Error: invalid register
>>>>> 'atomctl' for 'wsr' instruction
>>>
>>> --
>>> 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'
>>
>> Are they really matter? Or I can shut these errors up.
>
>Looks like I haven't supplied you with the compiler for test_kc705_hifi, for
>which these errors are reported. I've built it and put it here:
>
> http://jcmvbkbc.spb.ru/~jcmvbkbc/tmp/201604261801/x86_64-gcc-5.3.0-nolibc-xtensa-test_kc705_hifi-elf.tar.xz
>
>Please integrate it into your system along with other xtensa compilers.
OK, done. :)
Thanks,
Fengguang
next prev parent reply other threads:[~2016-07-26 4:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 10:32 kbuild test robot
2016-07-22 12:44 ` [kbuild-all] " Fengguang Wu
2016-07-25 23:20 ` Max Filippov
2016-07-26 4:42 ` Fengguang Wu [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-20 5:34 kbuild test robot
2016-03-20 11:54 ` Max Filippov
2016-03-22 2:17 ` [kbuild-all] " Fengguang Wu
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=20160726044257.GA29614@wfg-t540p.sh.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 \
--cc=philip.li@intel.com \
/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®