From: Nick Desaulniers <ndesaulniers@google.com>
To: Kees Cook <keescook@chromium.org>
Cc: Dan Li <ashimida@linux.alibaba.com>,
ardb@kernel.org, ojeda@kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Jonathan Corbet <corbet@lwn.net>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Nathan Chancellor <nathan@kernel.org>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-security-module@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH 0/2] gcc-plugins: Explicitly document purpose and deprecation schedule
Date: Wed, 20 Oct 2021 10:50:29 -0700 [thread overview]
Message-ID: <CAKwvOdnH4JG1Qt3scCVYGMT+iyfYKna4wyuODXZqURVfe+DZVg@mail.gmail.com> (raw)
In-Reply-To: <20211020173554.38122-1-keescook@chromium.org>
On Wed, Oct 20, 2021 at 10:35 AM Kees Cook <keescook@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@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
next prev parent reply other threads:[~2021-10-20 17:50 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
2021-10-20 19:10 ` Kees Cook
2021-10-20 17:50 ` Nick Desaulniers [this message]
2021-10-21 10:28 ` [PATCH 0/2] gcc-plugins: Explicitly document purpose and deprecation schedule 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=CAKwvOdnH4JG1Qt3scCVYGMT+iyfYKna4wyuODXZqURVfe+DZVg@mail.gmail.com \
--to=ndesaulniers@google.com \
--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=nathan@kernel.org \
--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).