From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: ARMv4 (not v4t) marked obsolete in gcc-6
Date: Thu, 10 Mar 2016 17:09:00 +0000 [thread overview]
Message-ID: <20160310170859.GR19428@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201603101759.37183.arnd@arndb.de>
On Thu, Mar 10, 2016 at 05:59:37PM +0100, Arnd Bergmann wrote:
> On Thursday 10 March 2016, Russell King - ARM Linux wrote:
> > On Thu, Mar 10, 2016 at 10:13:04AM +0100, Arnd Bergmann wrote:
> > > * RiscPC, Footbridge, EBSA110: Classic systems that used to be popular in
> > > the past but only remain in small quantities as far as I know. Russell still
> > > uses them. He also uses older compilers, so probably isn't affected
> > > immediately.
> >
> > And I'm unlikely to ever move off them, unless there's some miraculous
> > change which means I end up with server type systems to replace them.
> > That's been very unlikely for some time, as there's little interest in
> > hardware people producing such platforms and I'm no longer in a position
> > where, even if someone did, I'd end up with such hardware.
> >
> > So I'm pretty much stuck with what I have unless I replace it with x86
> > systems.
>
> Which compiler version do you have at the moment on those? Are you also
> stuck on OABI for the same reasons?
Well, the compiler version on the platforms is irrelevant as they're
cross-built kernels, for which I'm currently using gcc 4.7.4 for all
kernel builds.
The platforms themselves are pretty much stuck on OABI for ever
because there's no way to progressively convert them to EABI in a
sane manner.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-03-10 17:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 9:13 ARMv4 (not v4t) marked obsolete in gcc-6 Arnd Bergmann
2016-03-10 9:31 ` Russell King - ARM Linux
2016-03-10 16:59 ` Arnd Bergmann
2016-03-10 17:09 ` Russell King - ARM Linux [this message]
2016-03-10 17:59 ` Arnd Bergmann
2016-03-10 9:38 ` Dmitry Eremin-Solenikov
2016-03-10 16:38 ` Arnd Bergmann
2016-03-10 21:49 ` Dmitry Eremin-Solenikov
2016-03-15 15:14 ` Arnd Bergmann
2016-03-10 9:40 ` Baruch Siach
2016-03-10 10:58 ` Robin Murphy
2016-03-10 15:40 ` Dave Martin
2016-03-11 5:44 ` Hans Ulli Kroll
2016-03-11 6:48 ` [OpenWrt-Devel] " John Crispin
2016-03-11 16:09 ` Roman Yeryomin
2016-03-11 16:56 ` Hans Ulli Kroll
2016-03-15 15:59 ` Arnd Bergmann
2016-03-15 17:01 ` John Crispin
2016-03-15 20:26 ` Ard Biesheuvel
2016-03-15 22:00 ` Arnd Bergmann
2016-03-17 16:18 ` Ramana Radhakrishnan
2016-03-17 19:34 ` Dmitry Eremin-Solenikov
2016-03-18 13:25 ` Ramana Radhakrishnan
2016-03-21 20:50 ` Arnd Bergmann
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=20160310170859.GR19428@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).