[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20211020173554.38122-1-keescook@chromium.org>
Date: Wed, 20 Oct 2021 10:35:52 -0700
From: Kees Cook <keescook@...omium.org>
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>,
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@...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: [PATCH 0/2] gcc-plugins: Explicitly document purpose and deprecation schedule
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
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