linux-kernel - Re: [PATCH] gcc: clamp gcc version to most highest specific header version available

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] [day] [month] [year] [list]

Message-ID: <1409956708.5306.35.camel@localhost>
Date:	Sat, 06 Sep 2014 00:38:28 +0200
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Joe Perches <joe@...ches.com>
Cc:	linux-kernel@...r.kernel.org, Aaro Koskinen <aaro.koskinen@....fi>,
	Sasha Levin <sasha.levin@...cle.com>, akpm@...uxfoundation.org,
	mingo@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
	Richard Weinberger <richard.weinberger@...il.com>
Subject: Re: [PATCH] gcc: clamp gcc version to most highest specific header
 version available

On Fr, 2014-09-05 at 14:09 -0700, Joe Perches wrote:
> On Fri, 2014-09-05 at 22:39 +0200, Hannes Frederic Sowa wrote:
> > As announced in [1] gcc will increase its major number yearly but we don't
> > need to include gcc version specific quirks for every version normally.
> > 
> > This patch allows to compile every kernel with all new versions of gcc
> > without adding a specific compiler-gccX.h header. We do so by clamping
> > the __GNUC__ version to the most specific version dependent header file.
> > 
> > If someone adds a new gccX.h file __GCC_CLAMP_VERSION_HEADER also needs
> > to be modified.
> > 
> > The decision if chained including of header files (e.g. gcc5.h includes
> > gcc4.h) is necessary or should be avoided can be postponed until more
> > experience in using the official gcc release is gained.
> 
> I think the churn rate in the gcc compiler specific
> #include headers will be low enough that a single
> combined file should be acceptable.
> 
> Keeping all the gcc #defines together seems more
> readable to me.
> 
> The trivial integration I did eliminated one
> duplicate #define as well as that hack for
> #include gcc_header(__GNUC__)

It's just a proposal and I don't have a strong opinion on that. I just
want to make sure it is easy to compile current kernel with a gcc
released in two years. ;)

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/