From: Nathan Chancellor <nathan@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-hardening@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-doc@vger.kernel.org, Dan Li <ashimida@linux.alibaba.com>,
ardb@kernel.org, ojeda@kernel.org,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH 2/2] gcc-plugins: Remove cyc_complexity
Date: Wed, 20 Oct 2021 10:48:59 -0700 [thread overview]
Message-ID: <YXBWi/bCQoddzXB6@archlinux-ax161> (raw)
In-Reply-To: <20211020173554.38122-3-keescook@chromium.org>
On Wed, Oct 20, 2021 at 10:35:54AM -0700, Kees Cook wrote:
> This plugin has no impact on the resulting binary, is disabled
> under COMPILE_TEST, and is not enabled on any builds I'm aware of.
> Additionally, given the clarified purpose of GCC plugins in the kernel,
> remove cyc_complexity.
>
> Cc: Masahiro Yamada <masahiroy@kernel.org>
> Cc: Michal Marek <michal.lkml@markovi.net>
> Cc: Nick Desaulniers <ndesaulniers@google.com>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-hardening@vger.kernel.org
> Cc: linux-kbuild@vger.kernel.org
> Cc: linux-doc@vger.kernel.org
> Signed-off-by: Kees Cook <keescook@chromium.org>
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
One comment below.
> ---
> Documentation/kbuild/gcc-plugins.rst | 2 -
> scripts/Makefile.gcc-plugins | 2 -
> scripts/gcc-plugins/Kconfig | 16 -----
> scripts/gcc-plugins/cyc_complexity_plugin.c | 69 ---------------------
> 4 files changed, 89 deletions(-)
> delete mode 100644 scripts/gcc-plugins/cyc_complexity_plugin.c
>
> diff --git a/Documentation/kbuild/gcc-plugins.rst b/Documentation/kbuild/gcc-plugins.rst
> index 4b28c7a4032f..0ba76719f1b9 100644
> --- a/Documentation/kbuild/gcc-plugins.rst
> +++ b/Documentation/kbuild/gcc-plugins.rst
> @@ -96,7 +96,6 @@ Enable the GCC plugin infrastructure and some plugin(s) you want to use
> in the kernel config::
>
> CONFIG_GCC_PLUGINS=y
> - CONFIG_GCC_PLUGIN_CYC_COMPLEXITY=y
> CONFIG_GCC_PLUGIN_LATENT_ENTROPY=y
> ...
>
There is a comment about the cyc_complexity plugin at the very end of
this file that should also be removed it seems:
"See the cyc_complexity_plugin.c (CONFIG_GCC_PLUGIN_CYC_COMPLEXITY) GCC plugin."
> @@ -115,4 +114,3 @@ The GCC plugins are in scripts/gcc-plugins/. You need to put plugin source files
> right under scripts/gcc-plugins/. Creating subdirectories is not supported.
> It must be added to scripts/gcc-plugins/Makefile, scripts/Makefile.gcc-plugins
> and a relevant Kconfig file.
> -See the cyc_complexity_plugin.c (CONFIG_GCC_PLUGIN_CYC_COMPLEXITY) GCC plugin.
> diff --git a/scripts/Makefile.gcc-plugins b/scripts/Makefile.gcc-plugins
> index 952e46876329..6583ecf2e674 100644
> --- a/scripts/Makefile.gcc-plugins
> +++ b/scripts/Makefile.gcc-plugins
> @@ -1,7 +1,5 @@
> # SPDX-License-Identifier: GPL-2.0
>
> -gcc-plugin-$(CONFIG_GCC_PLUGIN_CYC_COMPLEXITY) += cyc_complexity_plugin.so
> -
> gcc-plugin-$(CONFIG_GCC_PLUGIN_LATENT_ENTROPY) += latent_entropy_plugin.so
> gcc-plugin-cflags-$(CONFIG_GCC_PLUGIN_LATENT_ENTROPY) \
> += -DLATENT_ENTROPY_PLUGIN
> diff --git a/scripts/gcc-plugins/Kconfig b/scripts/gcc-plugins/Kconfig
> index 3f5d3580ec06..821a725a7f5c 100644
> --- a/scripts/gcc-plugins/Kconfig
> +++ b/scripts/gcc-plugins/Kconfig
> @@ -19,22 +19,6 @@ menuconfig GCC_PLUGINS
>
> if GCC_PLUGINS
>
> -config GCC_PLUGIN_CYC_COMPLEXITY
> - bool "Compute the cyclomatic complexity of a function" if EXPERT
> - depends on !COMPILE_TEST # too noisy
> - help
> - The complexity M of a function's control flow graph is defined as:
> - M = E - N + 2P
> - where
> -
> - E = the number of edges
> - N = the number of nodes
> - P = the number of connected components (exit nodes).
> -
> - Enabling this plugin reports the complexity to stderr during the
> - build. It mainly serves as a simple example of how to create a
> - gcc plugin for the kernel.
> -
> config GCC_PLUGIN_SANCOV
> bool
> # Plugin can be removed once the kernel only supports GCC 6.1.0+
> diff --git a/scripts/gcc-plugins/cyc_complexity_plugin.c b/scripts/gcc-plugins/cyc_complexity_plugin.c
> deleted file mode 100644
> index 73124c2b3edd..000000000000
> --- a/scripts/gcc-plugins/cyc_complexity_plugin.c
> +++ /dev/null
> @@ -1,69 +0,0 @@
> -/*
> - * Copyright 2011-2016 by Emese Revfy <re.emese@gmail.com>
> - * Licensed under the GPL v2, or (at your option) v3
> - *
> - * Homepage:
> - * https://github.com/ephox-gcc-plugins/cyclomatic_complexity
> - *
> - * https://en.wikipedia.org/wiki/Cyclomatic_complexity
> - * The complexity M is then defined as:
> - * M = E - N + 2P
> - * where
> - *
> - * E = the number of edges of the graph
> - * N = the number of nodes of the graph
> - * P = the number of connected components (exit nodes).
> - *
> - * Usage (4.5 - 5):
> - * $ make clean; make run
> - */
> -
> -#include "gcc-common.h"
> -
> -__visible int plugin_is_GPL_compatible;
> -
> -static struct plugin_info cyc_complexity_plugin_info = {
> - .version = "20160225",
> - .help = "Cyclomatic Complexity\n",
> -};
> -
> -static unsigned int cyc_complexity_execute(void)
> -{
> - int complexity;
> - expanded_location xloc;
> -
> - /* M = E - N + 2P */
> - complexity = n_edges_for_fn(cfun) - n_basic_blocks_for_fn(cfun) + 2;
> -
> - xloc = expand_location(DECL_SOURCE_LOCATION(current_function_decl));
> - fprintf(stderr, "Cyclomatic Complexity %d %s:%s\n", complexity,
> - xloc.file, DECL_NAME_POINTER(current_function_decl));
> -
> - return 0;
> -}
> -
> -#define PASS_NAME cyc_complexity
> -
> -#define NO_GATE
> -#define TODO_FLAGS_FINISH TODO_dump_func
> -
> -#include "gcc-generate-gimple-pass.h"
> -
> -__visible int plugin_init(struct plugin_name_args *plugin_info, struct plugin_gcc_version *version)
> -{
> - const char * const plugin_name = plugin_info->base_name;
> -
> - PASS_INFO(cyc_complexity, "ssa", 1, PASS_POS_INSERT_AFTER);
> -
> - if (!plugin_default_version_check(version, &gcc_version)) {
> - error(G_("incompatible gcc/plugin versions"));
> - return 1;
> - }
> -
> - register_callback(plugin_name, PLUGIN_INFO, NULL,
> - &cyc_complexity_plugin_info);
> - register_callback(plugin_name, PLUGIN_PASS_MANAGER_SETUP, NULL,
> - &cyc_complexity_pass_info);
> -
> - return 0;
> -}
> --
> 2.30.2
>
next prev parent reply other threads:[~2021-10-20 17:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 17:35 [PATCH 0/2] gcc-plugins: Explicitly document purpose and deprecation schedule Kees Cook
2021-10-20 17:35 ` [PATCH 1/2] " Kees Cook
2021-10-20 17:44 ` Miguel Ojeda
2021-10-20 19:12 ` Kees Cook
2021-10-20 17:45 ` Nathan Chancellor
2021-10-20 19:15 ` Kees Cook
2021-10-20 17:35 ` [PATCH 2/2] gcc-plugins: Remove cyc_complexity Kees Cook
2021-10-20 17:48 ` Miguel Ojeda
2021-10-20 19:11 ` Kees Cook
2021-10-20 17:48 ` Nathan Chancellor [this message]
2021-10-20 19:10 ` Kees Cook
2021-10-20 17:50 ` [PATCH 0/2] gcc-plugins: Explicitly document purpose and deprecation schedule Nick Desaulniers
2021-10-21 10:28 ` Ard Biesheuvel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YXBWi/bCQoddzXB6@archlinux-ax161 \
--to=nathan@kernel.org \
--cc=ardb@kernel.org \
--cc=ashimida@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=serge@hallyn.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).