From: Michal Marek <mmarek@suse.cz>
To: Andi Kleen <andi@firstfloor.org>
Cc: akpm@linux-foundation.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH] Support gcc 6 for building
Date: Thu, 16 Apr 2015 09:57:48 +0200 [thread overview]
Message-ID: <552F6B7C.7020406@suse.cz> (raw)
In-Reply-To: <1429127143-31745-1-git-send-email-andi@firstfloor.org>
On 2015-04-15 21:45, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
>
> gcc recently switched to a new version number scheme, where every version
> gets a new major version number. The current version is 5.x, the next 6.x, etc.
>
> The gcc git repository trunk branch just switched to report 6.x for the next
> major release.
>
> This breaks the way Linux selects compiler-gccX.h based on the major
> version. Every new version would require adding a new compiler-gccX.h file,
> which wouldn't really scale.
>
> Let's assume that future gccs are fairly compatible (they are unlikely
> to break anything Linux is relying on). So we can just keep using
> compiler-gcc5.h, and select any specific differences with #if.
Good idea. With the new scheme, we could also merge back compiler-gcc5.h
and compiler-gcc4.h. The only difference is the KASAN_ABI_VERSION define.
Michal
next prev parent reply other threads:[~2015-04-16 7:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 19:45 [PATCH] Support gcc 6 for building Andi Kleen
2015-04-16 3:04 ` Segher Boessenkool
2015-04-16 7:57 ` Michal Marek [this message]
2015-04-16 15:56 ` Andi Kleen
2015-04-16 16:23 ` Joe Perches
2015-04-16 16:29 ` Andi Kleen
2015-04-16 20:31 ` [PATCH 0/2] Integrate compiler-gcc[345].h files into compiler-gcc.h Joe Perches
2015-04-16 20:31 ` [PATCH 1/2] compiler-gcc.h: Neatening Joe Perches
2015-04-16 20:44 ` Joe Perches
2015-04-16 20:31 ` [PATCH 2/2] compiler-gcc: Integrate the various compiler-gcc[345].h files Joe Perches
2015-04-20 21:17 ` [PATCH 0/2] Integrate compiler-gcc[345].h files into compiler-gcc.h Andrew Morton
2015-04-20 21:24 ` Andi Kleen
2015-04-16 20:13 ` [PATCH] Support gcc 6 for building Michal Marek
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=552F6B7C.7020406@suse.cz \
--to=mmarek@suse.cz \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=segher@kernel.crashing.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).