[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMj1kXEw2P+Q2Nd-+vf6U5apx+v5Q4TTW6y0m-MFaB1O2OAehQ@mail.gmail.com>
Date: Thu, 21 Oct 2021 12:28:09 +0200
From: Ard Biesheuvel <ardb@...nel.org>
To: Kees Cook <keescook@...omium.org>
Cc: Dan Li <ashimida@...ux.alibaba.com>,
Miguel Ojeda <ojeda@...nel.org>,
Masahiro Yamada <masahiroy@...nel.org>,
Michal Marek <michal.lkml@...kovi.net>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Jonathan Corbet <corbet@....net>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Nathan Chancellor <nathan@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-hardening@...r.kernel.org,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Doc Mailing List <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, 20 Oct 2021 at 19:35, 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. :)
>
> Thanks!
>
> -Kees
>
>
> Kees Cook (2):
> gcc-plugins: Explicitly document purpose and deprecation schedule
> gcc-plugins: Remove cyc_complexity
>
Acked-by: Ard Biesheuvel <ardb@...nel.org>
> 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
>
Powered by blists - more mailing lists