From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [Suggestion] Latest randconfig build errors for Head.S
Date: Fri, 15 Mar 2013 10:56:55 +0000 [thread overview]
Message-ID: <201303151056.55819.arnd@arndb.de> (raw)
In-Reply-To: <CAAQYJAvXLV38shKncAKKqgQ9G0SnXjh+=aJHBdhd29yzVtL80A@mail.gmail.com>
On Friday 15 March 2013, Andrea Adami wrote:
> On Fri, Mar 15, 2013 at 1:52 AM, Chen Gang <gang.chen@asianux.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
next prev parent reply other threads:[~2013-03-15 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 4:38 [Suggestion] Latest randconfig build errors for Head.S Chen Gang
2013-03-14 23:43 ` Russell King - ARM Linux
2013-03-15 0:52 ` Chen Gang
2013-03-15 9:31 ` Andrea Adami
2013-03-15 10:36 ` Chen Gang
2013-03-15 10:56 ` Arnd Bergmann [this message]
2013-03-15 11:11 ` Chen Gang F T
2013-03-15 11:29 ` Arnd Bergmann
2013-03-17 2:31 ` Chen Gang F T
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=201303151056.55819.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).