From: robin.murphy@arm•com (Robin Murphy)
To: linux-arm-kernel@lists•infradead.org
Subject: ARMv4 (not v4t) marked obsolete in gcc-6
Date: Thu, 10 Mar 2016 10:58:29 +0000 [thread overview]
Message-ID: <56E15355.1040908@arm.com> (raw)
In-Reply-To: <20160310094000.GA2057@tarshish>
Hi Baruch,
On 10/03/16 09:40, Baruch Siach wrote:
> Hi Arnd,
>
> On Thu, Mar 10, 2016 at 10:13:04AM +0100, Arnd Bergmann wrote:
>> 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.
>>
>> We will of course be able to compile kernels for a long time using older compilers, but
>> this tends to get harder over the years as people upgrade to newer distros.
>>
>> Here is an overview of which ARMv4 platforms we still have as of Linux-4.6:
>>
>> * Moxart: this is the only one that was recently (2013) added, and is apparently
>> hardware that remains commercially available.
>>
>> * Gemini: officially supported in OpenWRT today, with the latest compiler. This one
>> will likely cause the most issues for actual users. It would be helpful to get
>> some numbers about users or downloads here, to see whether it can be dropped
>> in a future OpenWRT release or if it might be possible to leave this on
>> gcc-6.x when the other platforms move on to gcc-7+
>>
>> * sa1100: A lot of people have these, but I'm guessing this is mostly interesting
>> for hobbyists that are able to keep using older gcc versions.
>>
>> * 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.
>
> There are also quite a few ARM920T (ARMv4) based SoCs: EP93xx, Atmel
> AT91RM9200, Samsung S3C24xx, Freescale i.MX1.
ARM920T is, as the "T" suggests, v4t, not v4, hence unaffected. It's
only pre-Thumb architectures that GCC wants to drop.
Robin.
>
> baruch
>
next prev parent reply other threads:[~2016-03-10 10:58 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
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 [this message]
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=56E15355.1040908@arm.com \
--to=robin.murphy@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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