From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754444AbcGZEnG (ORCPT ); Tue, 26 Jul 2016 00:43:06 -0400 Received: from mga04.intel.com ([192.55.52.120]:59128 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751723AbcGZEnD (ORCPT ); Tue, 26 Jul 2016 00:43:03 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,422,1464678000"; d="scan'208";a="853473181" Date: Tue, 26 Jul 2016 12:42:57 +0800 From: Fengguang Wu To: Max Filippov Cc: Chris Zankel , kbuild-all@01.org, LKML , Philip Li Subject: Re: [kbuild-all] arch/xtensa/include/asm/initialize_mmu.h:55: Error: invalid register 'atomctl' for 'wsr' instruction Message-ID: <20160726044257.GA29614@wfg-t540p.sh.intel.com> References: <201607221826.7SNz0708%fengguang.wu@intel.com> <20160722124411.GC32690@wfg-t540p.sh.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 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