From: "Arnd Bergmann" <arnd@arndb.de>
To: "Kees Cook" <kees@kernel.org>
Cc: "Jeff Johnson" <quic_jjohnson@quicinc.com>,
linux-hardening@vger.kernel.org,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: mips gcc plugin issues
Date: Thu, 20 Jun 2024 07:10:13 +0200 [thread overview]
Message-ID: <345dff33-86f0-4de3-90e3-9e3a13f20875@app.fastmail.com> (raw)
In-Reply-To: <202406191414.67C589A@keescook>
On Wed, Jun 19, 2024, at 23:17, Kees Cook wrote:
> On Wed, Jun 19, 2024 at 11:12:25PM +0200, Arnd Bergmann wrote:
>> On Wed, Jun 19, 2024, at 22:50, Kees Cook wrote:
>> The problem here is that a gcc plugin links against the
>> compiler, not against code produced by it. I'm linking the
>> crosstool compilers statically against libraries as much as
>> possible in order to make them more portable between distros,
>> but the downside of that is that plugins will only work in
>> the environment that I was using to build these toolchains.
>>
>> My build environment is an older Debian (in order to be
>> portable to old glibc versions), but with the system compiler
>> updated to gcc-13 (since x86 libgcc cannot be cross-compiled
>> with an older compiler).
>
> Can the crosstools remove the plugin support? That seems like the best
> solution. Kconfig test for plugin availability with:
>
> depends on $(success,test -e $(shell,$(CC)
> -print-file-name=plugin)/include/plugin-version.h)
Good idea, yes. I still have to upload gcc-14.1 and gcc-13.3 binaries
anyway, so I'll try turning off plugin support when I build it.
Arnd
prev parent reply other threads:[~2024-06-20 5:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 23:41 mips gcc plugin issues Jeff Johnson
2024-06-19 20:50 ` Kees Cook
2024-06-19 21:12 ` Arnd Bergmann
2024-06-19 21:17 ` Kees Cook
2024-06-20 5:10 ` Arnd Bergmann [this message]
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=345dff33-86f0-4de3-90e3-9e3a13f20875@app.fastmail.com \
--to=arnd@arndb.de \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_jjohnson@quicinc.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