All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Joe Perches <joe@perches.com>,
	Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
	akpm@linuxfoundation.org, mingo@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel: add support for gcc 5
Date: Thu, 04 Sep 2014 23:37:04 -0400	[thread overview]
Message-ID: <54092FE0.3030004@oracle.com> (raw)
In-Reply-To: <1409874455.2770.26.camel@joe-AO725>

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.


Thanks,
Sasha

  reply	other threads:[~2014-09-05  3:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 15:37 [PATCH] kernel: add support for gcc 5 Sasha Levin
2014-09-04 21:12 ` Andrew Morton
2014-09-04 21:19   ` Richard Weinberger
2014-09-04 21:25     ` Andrew Morton
2014-09-04 21:38       ` Sasha Levin
2014-09-05 15:04       ` H. Peter Anvin
2014-09-04 21:25 ` Aaro Koskinen
2014-09-04 21:32   ` Sasha Levin
2014-09-04 22:43   ` Hannes Frederic Sowa
2014-09-04 23:47     ` Joe Perches
2014-09-05  3:37       ` Sasha Levin [this message]
2014-09-05  3:58         ` Joe Perches
2014-09-05  4:08         ` Hannes Frederic Sowa
2014-09-05 14:44           ` Sasha Levin
2014-09-05 20:39             ` [PATCH] gcc: clamp gcc version to most highest specific header version available Hannes Frederic Sowa
2014-09-05 21:09               ` Joe Perches
2014-09-05 22:38                 ` Hannes Frederic Sowa

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=54092FE0.3030004@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=akpm@linuxfoundation.org \
    --cc=hannes@stressinduktion.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.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.