linux-kernel - Re: [PATCH] kernel: add support for gcc 5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1409870628.2310799.163815377.623F33D2@webmail.messagingengine.com>
Date:	Fri, 05 Sep 2014 00:43:48 +0200
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Aaro Koskinen <aaro.koskinen@....fi>,
	Sasha Levin <sasha.levin@...cle.com>
Cc:	akpm@...uxfoundation.org, mingo@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kernel: add support for gcc 5

Hello,

On Thu, Sep 4, 2014, at 23:25, Aaro Koskinen wrote:
> On Thu, Sep 04, 2014 at 11:37:19AM -0400, Sasha Levin wrote:
> > We're missing include/linux/compiler-gcc5.h which is required now
> > because gcc branched off to v5 in trunk.
> > 
> > Just copy the relevant bits out of include/linux/compiler-gcc4.h,
> > no new code is added as of now.
> > 
> > This fixes a build error when using gcc 5.
> 
> With the new GCC version numbering scheme, does this mean there will
> be a new such file to be added every year? Maybe this could be handled
> some other way?

I agree, with the new gcc roadmap announced back in August [1] they tend
to increase the major number with each yearly release. I don't think it
is feasable to add a new header every year in a timely manner.

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? ;)

[1] https://gcc.gnu.org/develop.html (Section "Version Numbering Scheme
for GCC 5 and Up")

Bye,
Hannes
--
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/