From: Max Filippov <jcmvbkbc@gmail.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Piet Delaney <piet.delaney@gmail.com>,
kbuild-all@01.org, LKML <linux-kernel@vger.kernel.org>,
Chris Zankel <chris@zankel.net>
Subject: Re: arch/xtensa/include/asm/processor.h:227: Error: unknown opcode or format name 'wer'
Date: Mon, 18 Apr 2016 18:52:57 +0300 [thread overview]
Message-ID: <CAMo8Bf+hqOUCTnxxJrHf7BDziCkRgib9513BkCVASf-wG6D1Ag@mail.gmail.com> (raw)
In-Reply-To: <201604182329.IPfs4joE%fengguang.wu@intel.com>
Hi Fengguang,
On Mon, Apr 18, 2016 at 6:29 PM, kbuild test robot
<fengguang.wu@intel.com> wrote:
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: c3b46c73264b03000d1e18b22f5caf63332547c9
> commit: 2c684d892bb2ee31cc48f4a8b91e86a0f15e82f9 xtensa: add Three Core HiFi-2 MX Variant.
> date: 5 weeks ago
> config: xtensa-smp_lx200_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 2c684d892bb2ee31cc48f4a8b91e86a0f15e82f9
> # save the attached .config to linux build tree
> make.cross ARCH=xtensa
>
> All errors (new ones prefixed by >>):
>
> arch/xtensa/include/asm/processor.h: Assembler messages:
>>> arch/xtensa/include/asm/processor.h:227: Error: unknown opcode or format name 'wer'
>>> arch/xtensa/include/asm/processor.h:227: Error: unknown opcode or format name 'wer'
>>> arch/xtensa/include/asm/processor.h:227: Error: unknown opcode or format name 'wer'
As I said before these are not errors in the linux code, that's
a result of using a compiler not configured for this specific xtensa core.
How can I help to fix it?
--
Thanks.
-- Max
next prev parent reply other threads:[~2016-04-18 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 15:29 arch/xtensa/include/asm/processor.h:227: Error: unknown opcode or format name 'wer' kbuild test robot
2016-04-18 15:52 ` Max Filippov [this message]
2016-04-19 1:43 ` Philip Li
2016-04-19 1:52 ` [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=CAMo8Bf+hqOUCTnxxJrHf7BDziCkRgib9513BkCVASf-wG6D1Ag@mail.gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=chris@zankel.net \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piet.delaney@gmail.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;
as well as URLs for NNTP newsgroup(s).