[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKwvOdnH4JG1Qt3scCVYGMT+iyfYKna4wyuODXZqURVfe+DZVg@mail.gmail.com>
Date: Wed, 20 Oct 2021 10:50:29 -0700
From: Nick Desaulniers <ndesaulniers@...gle.com>
To: Kees Cook <keescook@...omium.org>
Cc: Dan Li <ashimida@...ux.alibaba.com>, ardb@...nel.org,
ojeda@...nel.org, Masahiro Yamada <masahiroy@...nel.org>,
Michal Marek <michal.lkml@...kovi.net>,
Jonathan Corbet <corbet@....net>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Nathan Chancellor <nathan@...nel.org>,
linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org,
linux-kbuild@...r.kernel.org, linux-doc@...r.kernel.org,
linux-security-module@...r.kernel.org, llvm@...ts.linux.dev
Subject: Re: [PATCH 0/2] gcc-plugins: Explicitly document purpose and
deprecation schedule
On Wed, Oct 20, 2021 at 10:35 AM Kees Cook <keescook@...omium.org> wrote:
>
> Hi,
>
> GCC plugins should only exist when some compiler feature needs to be
> proven but does not exist in either GCC nor Clang. For example, if a
> desired feature is already in Clang, it should be added to GCC upstream.
> Document this explicitly.
>
> I'll put this in -next unless there are objections. :)
Acked-by: Nick Desaulniers <ndesaulniers@...gle.com>
>
> Thanks!
>
> -Kees
>
>
> Kees Cook (2):
> gcc-plugins: Explicitly document purpose and deprecation schedule
> gcc-plugins: Remove cyc_complexity
>
> Documentation/kbuild/gcc-plugins.rst | 28 ++++++++-
> scripts/Makefile.gcc-plugins | 2 -
> scripts/gcc-plugins/Kconfig | 20 +-----
> scripts/gcc-plugins/cyc_complexity_plugin.c | 69 ---------------------
> security/Kconfig.hardening | 9 ++-
> 5 files changed, 34 insertions(+), 94 deletions(-)
> delete mode 100644 scripts/gcc-plugins/cyc_complexity_plugin.c
>
> --
> 2.30.2
>
--
Thanks,
~Nick Desaulniers
Powered by blists - more mailing lists