From: "Arnd Bergmann" <arnd@arndb.de>
To: "Mark Brown" <broonie@kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Kees Cook" <kees@kernel.org>, "Mickaël Salaün" <mic@digikod.net>,
"Günther Noack" <gnoack@google.com>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] gcc-plugins: Disable GCC plugins for compile test builds
Date: Wed, 09 Apr 2025 21:24:15 +0200 [thread overview]
Message-ID: <3c3365f2-96f8-40c1-ab8b-2bd17b9b7d87@app.fastmail.com> (raw)
In-Reply-To: <815b2990-570a-4603-b33f-2af1f0851434@sirena.org.uk>
On Wed, Apr 9, 2025, at 20:09, Mark Brown wrote:
> On Wed, Apr 09, 2025 at 10:42:19AM -0700, Linus Torvalds wrote:
>
> Yeah. The other problem we have is that AFAIK unlike clang we don't
> really have people actively working on GCC coverage specifically,
> everyone mostly just assumes everyone else is doing it since GCC is the
> default (me being as guilty of that as everyone else here). The work
> Arnd's doing is the nearest thing I'm aware of but that's more
> intermittent and I gather his toolchains don't have plugins enabled
> which wouldn't help here.
Right, I don't think there is any sensible way to support plugins
with my cross compilers, because that requires building the plugin
on a developer's machine and link it against the compiler I statically
linked against a specific libstdc++ to avoid runtime compatibility
problems.
Arnd
next prev parent reply other threads:[~2025-04-09 19:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 20:57 [PATCH] gcc-plugins: Disable GCC plugins for compile test builds Mark Brown
2025-04-07 21:33 ` Linus Torvalds
2025-04-07 22:02 ` Mark Brown
2025-04-08 9:22 ` Arnd Bergmann
2025-04-08 20:37 ` Kees Cook
2025-04-10 7:58 ` Arnd Bergmann
2025-04-08 23:32 ` Kees Cook
2025-04-09 5:43 ` Arnd Bergmann
2025-04-09 12:19 ` Mark Brown
2025-04-09 15:33 ` Linus Torvalds
2025-04-09 17:29 ` Mark Brown
2025-04-09 17:42 ` Linus Torvalds
2025-04-09 17:46 ` Kees Cook
2025-04-09 18:09 ` Mark Brown
2025-04-09 19:24 ` Arnd Bergmann [this message]
2025-04-15 20:26 ` Palmer Dabbelt
2025-04-15 20:41 ` Mark Brown
2025-04-15 20:43 ` Kees Cook
2025-04-15 20:41 ` Kees Cook
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=3c3365f2-96f8-40c1-ab8b-2bd17b9b7d87@app.fastmail.com \
--to=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=gnoack@google.com \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=torvalds@linux-foundation.org \
/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