lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 18 Apr 2016 18:52:57 +0300
From:	Max Filippov <jcmvbkbc@...il.com>
To:	kbuild test robot <fengguang.wu@...el.com>
Cc:	Piet Delaney <piet.delaney@...il.com>, kbuild-all@...org,
	LKML <linux-kernel@...r.kernel.org>,
	Chris Zankel <chris@...kel.net>
Subject: Re: arch/xtensa/include/asm/processor.h:227: Error: unknown opcode or
 format name 'wer'

Hi Fengguang,

On Mon, Apr 18, 2016 at 6:29 PM, kbuild test robot
<fengguang.wu@...el.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

Powered by blists - more mailing lists