linux-kernel - Re: [PATCH] gcc-plugins: Disable GCC plugins for compile test builds

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <3c3365f2-96f8-40c1-ab8b-2bd17b9b7d87@app.fastmail.com>
Date: Wed, 09 Apr 2025 21:24:15 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Mark Brown" <broonie@...nel.org>,
 "Linus Torvalds" <torvalds@...ux-foundation.org>
Cc: "Kees Cook" <kees@...nel.org>,
 Mickaël Salaün <mic@...ikod.net>,
 Günther Noack <gnoack@...gle.com>,
 linux-hardening@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-security-module@...r.kernel.org
Subject: Re: [PATCH] gcc-plugins: Disable GCC plugins for compile test builds

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