[PATCH 0/2] gcc-plugins: Explicitly document purpose and deprecation schedule
Nick Desaulniers
ndesaulniers at google.com
Wed Oct 20 17:50:29 UTC 2021
On Wed, Oct 20, 2021 at 10:35 AM Kees Cook <keescook at chromium.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 at google.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
More information about the Linux-security-module-archive
mailing list