From: Tony Luck <tony.luck@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
riel@surriel.com, Mike Galbraith <efault@gmx.de>,
Dave Hansen <dave.hansen@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Build failures with gcc 4.5 and older
Date: Tue, 14 Aug 2018 13:19:01 -0700 [thread overview]
Message-ID: <CA+8MBbJ=09jAHNZTFrwMFFGbUSWEMYCDxKTMvM2XE+daVa599g@mail.gmail.com> (raw)
In-Reply-To: <20180814173623.GA5117@roeck-us.net>
On Tue, Aug 14, 2018 at 11:02 AM Guenter Roeck <linux@roeck-us.net> wrote:
>
> On Tue, Aug 14, 2018 at 10:20:32AM -0700, Linus Torvalds wrote:
> > On Tue, Aug 14, 2018 at 10:09 AM Guenter Roeck <linux@roeck-us.net> wrote:
> > >
> > > Does that mean that gcc 4.5 and older are now officially no longer
> > > supported for compiling the kernel ?
> >
> > I guess we might as well make this the excuse for making that official.
> >
> > Maybe it's trivially fixable, but I don't even want to look at it,
> > since we've talked about updating the minimum gcc version so long.
> >
> > > If so, would it make sense to update include/linux/compiler-gcc.h
> > > accordingly ?
> >
> > Unless somebody cares, and comes with a trivial fix to make old
> > compilers happy, let's just do that.
> >
>
> Only implication is that it is the death warrant for unicore32,
> since the only compiler available for it is gcc 4.4.2.
My ia64 test box only has 4.3.4. I seem to remember some pain points
with newer versions of gcc on ia64. I need to poke around and find one
new enough to get past this problem, but that still works for kernel building.
-Tony
next prev parent reply other threads:[~2018-08-14 20:19 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 [this message]
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
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='CA+8MBbJ=09jAHNZTFrwMFFGbUSWEMYCDxKTMvM2XE+daVa599g@mail.gmail.com' \
--to=tony.luck@gmail.com \
--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=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).