All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: ARMv4 (not v4t) marked obsolete in gcc-6
Date: Thu, 10 Mar 2016 17:38:54 +0100	[thread overview]
Message-ID: <201603101738.55060.arnd@arndb.de> (raw)
In-Reply-To: <CALT56yPDXkOvwQHngFsLkjgkyGx5HRNj8oddhFjTRdMbv5zvbw@mail.gmail.com>

On Thursday 10 March 2016, Dmitry Eremin-Solenikov wrote:
> 2016-03-10 12:13 GMT+03:00 Arnd Bergmann <arnd@arndb.de>:
> > I've found out that ARMv3 and ARMv4 is now on track to get removed from gcc in the future,
> > so I'm trying to alert everyone that I have knowledge of using ARMv4 based platforms that
> > we currenly support in the Linux kernel.
> >
> > The architecture has been declared obsolete here: https://gcc.gnu.org/gcc-6/changes.html
> > and it will be removed in the following release (gcc-7) one year later, unless someone
> > raises concerns over it.
> 
> In which form should we raise concerns? Is it about stepping up as a
> maintainers, or just
> about telling them that platforms are used? 


As I understand it, having someone step up as an active maintainer would leave the
architecture supported indefinitely, while saying you still need the support
can at least delay the process a bit. Ramana can probably clarify further
what the gcc folks are looking for exactly.

> My main concern with
> limiting ARMv4 platforms
> to older compilers would be that sooner or later we won't be able to
> use newer kernels,
> as the mainline will stop supporting older compilers.

I think we've been doing ok with keeping old compilers working, gcc-4.2 
from 2007 seems to work fine for the older targets (it misses support for
some of the armv7 platforms in turn) and in theory we should be able to
get older ones working with a few patches: according to the README
file in the kernel, we support gcc-3.2 (from 2002) in theory, but I'm
running into some trickier problems with some of the older compilers.

It's definitely clear that at some point we will stop supporting gcc-6
for building the kernel, but I don't know if that's already 2022 or
only 2038 (when all sort of software breaks).

How long do you think you need for your systems?
Do you still ship new products, or are these all legacy devices that
will have a failing battery or flash at some point in the future?

	Arnd

  reply	other threads:[~2016-03-10 16:38 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
2016-03-10 17:59       ` Arnd Bergmann
2016-03-10  9:38 ` Dmitry Eremin-Solenikov
2016-03-10 16:38   ` Arnd Bergmann [this message]
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=201603101738.55060.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.