From: rob@landley.net (Rob Landley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Documentation/Changes: update binutils version requirement for ARMv7 builds
Date: Sun, 17 Nov 2013 12:50:21 -0600 [thread overview]
Message-ID: <1384714221.1974.276@driftwood> (raw)
In-Reply-To: <alpine.DEB.2.02.1310300923080.12006@tamien> (from pwalmsley@nvidia.com on Wed Oct 30 11:27:07 2013)
On 10/30/2013 11:27:07 AM, Paul Walmsley wrote:
>
> ARMv7 builds now make use of the pldw opcode and the ".arch_extension
> mp"
> pragma. These aren't supported in binutils prior to 2.21. So, update
> Documentation/Changes accordingly.
ARMv7 support didn't _exist_ in the minimal binutils version, and ARMv8
support is newer still. Hexagon, microblaze, they've all shown up in
newer versions than the one that will build older architectures.
Annotating the global Documentation/Changes with every per-arch
requirement... not sure that's the right place for it.
I also note that the FSF's toolchain seems to be losing steam again,
and this time around EGCS is called LLVM. Now that http://ellcc.org is
self-hosting (and can even build native toolchains as of
http://ellcc.org/blog/?p=251) all they need is http://lld.llvm.org to
catch up and I think they've got a complete non-gnu toolchain capable
of building a linux system. (It already contains musl-libc.org, I'm
banging on toybox to provide a public domain busybox replacement...)
So there are larger issues in motion here. Noting armv7 requirements in
an arm-specific file makes sense. Annotating the top level one raises
the question of why not to do that for arc, unicore, openrisc, tile...
Rob
next prev parent reply other threads:[~2013-11-17 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 16:27 [PATCH] Documentation/Changes: update binutils version requirement for ARMv7 builds Paul Walmsley
2013-10-30 16:51 ` Russell King - ARM Linux
2013-11-17 18:50 ` Rob Landley [this message]
2013-11-18 16:56 ` Stephen Warren
2013-12-05 2:26 ` Rob Landley
2013-11-18 20:06 ` Paul Walmsley
2013-12-05 2:37 ` Rob Landley
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=1384714221.1974.276@driftwood \
--to=rob@landley.net \
--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