From: Arnd Bergmann <arnd@arndb.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Guenter Roeck <linux@roeck-us.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@surriel.com>, Mike Galbraith <efault@gmx.de>,
Dave Hansen <dave.hansen@intel.com>
Subject: Re: Build failures with gcc 4.5 and older
Date: Mon, 20 Aug 2018 18:00:10 +0200 [thread overview]
Message-ID: <CAK8P3a27TU0Y_2j3rR6=mxFh5pBeUjCHVzV2NHaj_WD9E1sKCw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1808201652420.1551@nanos.tec.linutronix.de>
On Mon, Aug 20, 2018 at 4:58 PM Thomas Gleixner <tglx@linutronix.de> wrote:
>
> On Tue, 14 Aug 2018, Guenter Roeck wrote:
> >
> > For my part I am all for making gcc 4.6 mandatory.
>
> No objections from my side.
gcc-4.6 is also what I suggested a while ago as a good choice for a new minimum
version, back then I met some objection, but as time passes these probably got
less important:
https://lkml.org/lkml/2016/12/16/174
To recap the distros that I looked at back then using gcc older than
4.6, I found four:
RHEL6: gcc-4.4
Debian 6: gcc-4.4
Ubuntu 10.04: gcc-4.4
SLES11: gcc-4.3
The first three are all finally EOL as of this month, only SLES11 with gcc-4.3
is still supported in principle:
Service Pack Release FCS Date General Ends LTSS Ends
SUSE Linux Enterprise Server 11 24 Mar 2009 31 Dec 2010 N/A
SUSE Linux Enterprise Server 11 SP1 02 Jun 2010 31 Aug 2012 30 Aug 2015
SUSE Linux Enterprise Server 11 SP2 29 Feb 2012 31 Jan 2014 30 Jan 2017
SUSE Linux Enterprise Server 11 SP3 01 Jul 2013 31 Jan 2016 30 Jan 2019
SUSE Linux Enterprise Server 11 SP4 15 Jul 2015 31 Mar 2019 31 Mar 2022
However, installing the disro's SDK package on SLES11-SP3 brings it up to
gcc-4.7, or gcc-5.2 for SP4, so this is unlikely to cause much of a problem any
more.
I also have some ideas for cleanups that can be done now, in particular
to deal with compiler warnings.
Arnd
next prev parent reply other threads:[~2018-08-20 16:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 17:09 Build failures with gcc 4.5 and older Guenter Roeck
2018-08-14 17:20 ` Linus Torvalds
2018-08-14 17:36 ` Guenter Roeck
2018-08-14 20:19 ` Tony Luck
2018-08-15 16:09 ` Tony Luck
2018-08-15 16:34 ` Linus Torvalds
2018-08-16 0:27 ` Guenter Roeck
2018-08-15 16:49 ` Guenter Roeck
2018-08-14 17:48 ` Joe Perches
2018-08-19 21:23 ` Kees Cook
2018-08-20 17:46 ` Nick Desaulniers
2018-08-20 18:34 ` Linus Torvalds
2018-08-14 21:36 ` Andrew Morton
2018-08-14 22:15 ` Guenter Roeck
2018-08-14 23:02 ` Andrew Morton
2018-08-14 23:20 ` Linus Torvalds
2018-08-15 1:02 ` Guenter Roeck
2018-08-20 14:53 ` Thomas Gleixner
2018-08-20 16:00 ` Arnd Bergmann [this message]
2018-08-15 12:40 ` David Laight
2018-08-15 15:44 ` Linus Torvalds
2018-08-15 16:18 ` David Laight
2018-08-15 16:33 ` Linus Torvalds
2018-08-16 9:17 ` David Laight
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='CAK8P3a27TU0Y_2j3rR6=mxFh5pBeUjCHVzV2NHaj_WD9E1sKCw@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=riel@surriel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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).