[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201303151056.55819.arnd@arndb.de>
Date: Fri, 15 Mar 2013 10:56:55 +0000
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Andrea Adami <andrea.adami@...il.com>,
Chen Gang <gang.chen@...anux.com>, matthew.leach@....com,
dave.martin@...aro.org,
"Russell King - ARM Linux" <linux@....linux.org.uk>,
nico@...aro.org, Will Deacon <will.deacon@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
matthew.gretton-dann@...aro.org
Subject: Re: [Suggestion] Latest randconfig build errors for Head.S
On Friday 15 March 2013, Andrea Adami wrote:
> On Fri, Mar 15, 2013 at 1:52 AM, Chen Gang <gang.chen@...anux.com> wrote:
> > 于 2013年03月15日 07:43, Russell King - ARM Linux 写道:
> >> So our wonderful toolchain has decided to start producing NULL warnings
> >> for every "mcr p15, 0, rX, c7, c10, 4" instruction? I'd just ignore
> >> them and hope that the toolchain people fix it.
>
> AFAIK Arnd is aware and waiting for feedback about his patch:
>
> ARM: compressed/head.S: work around new binutils warning Arnd Bergmann
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/144846.html
Right. The fact that as prints a warning for those instructions makes sense
given that we are telling it we want to run on *all* ARM architectures,
and that ARMv8 has deprecated them officially.
Of course, what is bogus about this is the "NULL" part rather than printing
the text that was meant to come out to explain the situation. I don't
know how to report that bug other than what I tried before, but if it gets
fixed by printing the right text, we will still want to build a kernel
without getting any warnings.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists