From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Pitre Subject: Re: Latest build results - errors/warnings - lots of them Date: Tue, 30 Apr 2013 11:12:12 -0400 (EDT) Message-ID: References: <20130430081739.GP14496@n2100.arm.linux.org.uk> <201304301304.20650.arnd@arndb.de> <20130430114229.GA2439@linaro.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from mail-qe0-f52.google.com ([209.85.128.52]:51983 "EHLO mail-qe0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759735Ab3D3PMS (ORCPT ); Tue, 30 Apr 2013 11:12:18 -0400 Received: by mail-qe0-f52.google.com with SMTP id q19so343729qeb.25 for ; Tue, 30 Apr 2013 08:12:16 -0700 (PDT) In-Reply-To: <20130430114229.GA2439@linaro.org> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Dave Martin Cc: Arnd Bergmann , Russell King - ARM Linux , Tony Lindgren , Catalin Marinas , linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org On Tue, 30 Apr 2013, Dave Martin wrote: > On Tue, Apr 30, 2013 at 01:04:20PM +0200, Arnd Bergmann wrote: > > On Tuesday 30 April 2013, Russell King - ARM Linux wrote: > > > Latest nightly build of 3.9+my for-next+arm-soc's for-next results in a > > > great load of new warnings and errors. arch/arm/common/mcpm_head.S, > > > arch/arm/common/mcpm_platsmp.c, arch/arm/common/vlock.S are the biggest > > > source of errors. > > [...] > > > >arch/arm/common/mcpm_head.S:39: Error: selected processor does not support ARM mode `ubfx r9,r0,#0,#8' > > >arch/arm/common/mcpm_head.S:40: Error: selected processor does not support ARM mode `ubfx r10,r0,#8,#8' > > >arch/arm/common/mcpm_head.S:100: Error: selected processor does not support ARM mode `dmb' > > >arch/arm/common/mcpm_head.S:115: Error: selected processor does not support ARM mode `dmb' > > >arch/arm/common/mcpm_head.S:127: Error: selected processor does not support ARM mode `dmb' > > >arch/arm/common/mcpm_head.S:131: Error: selected processor does not support ARM mode `dmb' > > >arch/arm/common/mcpm_head.S:138: Error: selected processor does not support ARM mode `dsb' > > >arch/arm/common/mcpm_head.S:152: Error: selected processor does not support ARM mode `dmb' > > >arch/arm/common/mcpm_head.S:161: Error: selected processor does not support ARM mode `dmb' > > >arch/arm/common/mcpm_head.S:175: Error: selected processor does not support ARM mode `dmb' > > >arch/arm/common/vlock.S:62: Error: selected processor does not support ARM mode `dmb' > > >arch/arm/common/vlock.S:72: Error: selected processor does not support ARM mode `dmb' > > >arch/arm/common/vlock.S:72: Error: selected processor does not support ARM mode `dsb' > > >arch/arm/common/vlock.S:89: Error: selected processor does not support ARM mode `dmb' > > >arch/arm/common/vlock.S:95: Error: selected processor does not support ARM mode `dmb' > > >arch/arm/common/vlock.S:95: Error: selected processor does not support ARM mode `dsb' > > >arch/arm/common/vlock.S:102: Error: selected processor does not support ARM mode `dmb' > > >arch/arm/common/vlock.S:105: Error: selected processor does not support ARM mode `dsb' > > > > Right, the problem here is that the code was never tested with an ARMv6+ARMv7 config. > > We can either fix it up by adding > > > > .arch armv7-a > > > > in the assembly files, or by doing the same in the Makefile: > > > > AFLAGS_vlock.S += -march=armv7-a > > AFLAGS_mcpm_head.S += -march=armv7-a > > > Hmmm, this code was tested with ARCH_MULTIPLATFORM, but it looks like > no v6 boards were configured in when testing that... > > > Assuming people are OK with the Makefile route, here's a patch for that, > build-tested with a v6+v7 ARCH_MULTIPLATFORM config. Isn't the .arch armv7-a route a bit cleaner? That would have been my choice, although I don't feel strongly about it. Nicolas