|
Date: Thu, 22 Feb 2018 19:45:41 +0100 From: Emese Revfy <re.emese@...il.com> To: Masahiro Yamada <yamada.masahiro@...ionext.com> Cc: linux-kbuild@...r.kernel.org, Linus Torvalds <torvalds@...ux-foundation.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Arnd Bergmann <arnd@...db.de>, Kees Cook <keescook@...omium.org>, Randy Dunlap <rdunlap@...radead.org>, Ulf Magnusson <ulfalizer@...il.com>, Sam Ravnborg <sam@...nborg.org>, Michal Marek <michal.lkml@...kovi.net>, kernel-hardening@...ts.openwall.com, linux-kernel@...r.kernel.org, keescook@...omium.org, kernel-hardening@...ts.openwall.com Subject: Re: [PATCH 20/23] gcc-plugins: always build plugins with C++ On Sat, 17 Feb 2018 03:38:48 +0900 Masahiro Yamada <yamada.masahiro@...ionext.com> wrote: > If the target compiler is GCC 4.8 or newer, plugins are compiled with > HOSTCXX. Otherwise, gcc-plugin.sh will select HOSTCC or HOSTCXX. > > To simpily things, let's decide GCC 4.8 is the requirement for GCC > pulgins. With this, plugins are always built with HOSTCXX. This is a > feature of advanced users, so this requirement whould not be not a big > issue. I disagree with such a decision. I think the gcc plugins should compile with older version because the kernel can be compiled with them too. The distros use these older versions as well and I can very well imagine that new plugins will extend these with backported features such as my sancov plugin. -- Emese
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.