[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1409889532.2770.30.camel@joe-AO725>
Date: Thu, 04 Sep 2014 20:58:52 -0700
From: Joe Perches <joe@...ches.com>
To: Sasha Levin <sasha.levin@...cle.com>
Cc: Hannes Frederic Sowa <hannes@...essinduktion.org>,
Aaro Koskinen <aaro.koskinen@....fi>, akpm@...uxfoundation.org,
mingo@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kernel: add support for gcc 5
On Thu, 2014-09-04 at 23:37 -0400, Sasha Levin wrote:
> On 09/04/2014 07:47 PM, Joe Perches wrote:
> > On Fri, 2014-09-05 at 00:43 +0200, Hannes Frederic Sowa wrote:
> >> > Most statements are already depending on GCC_VERSION, maybe we can just
> >> > unify all gcc specific headers to one, still trying to keep the file
> >> > organized? ;)
> > Maybe something like:
> >
> > gnu development of gcc will be more frequent and the use of
> > compiler-gcc<major>.h likely will not be convenient anymore.
> >
> > Integrate the individual compiler-gcc<major>.h files into
> > compiler-gcc.h.
>
> Please no. We have a similar file we maintain in our team that's supposed to
> do something very similar for kernel versions. It goes all the way back to
> 2.6.9 and it's a *horrible* mess.
>
> This is how compiler-gcc.h will end up looking in a while.
As gcc options are generally upward compatible,
I don't think it will but there's no great way
to predict the future.
It wouldn't be as complicated as say backports.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists