From: "Arnd Bergmann" <arnd@arndb.de>
To: "Kees Cook" <kees@kernel.org>, "Mark Brown" <broonie@kernel.org>
Cc: "Linus Torvalds" <torvalds@linux-foundation.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 07:43:38 +0200 [thread overview]
Message-ID: <a379dc7d-5bb0-415b-b690-1c2d9106d7ca@app.fastmail.com> (raw)
In-Reply-To: <202504081630.4CE88E855@keescook>
On Wed, Apr 9, 2025, at 01:32, Kees Cook wrote:
> I can reproduce this for GCC 14, but I can't reproduce this with GCC
> 13. Which minor release is failing for you? My GCC 13 is:
> gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
I see it with "x86_64-linux-gnu-gcc-12 (Debian 12.2.0-14) 12.2.0"
(cross-compiling from arm64).
Arnd
next prev parent reply other threads:[~2025-04-09 5:44 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 [this message]
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
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=a379dc7d-5bb0-415b-b690-1c2d9106d7ca@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