From: Erhard Furtner <erhard_f@mailbox.org>
To: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
"René Rebe" <rene@exactco.de>,
linux-kbuild@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH V2] modpost: Amend ppc64 save/restfpr symnames for -Os build
Date: Wed, 26 Nov 2025 01:16:16 +0100 [thread overview]
Message-ID: <7e955a64-2fe6-4b8e-b49e-c3f827029b2b@mailbox.org> (raw)
In-Reply-To: <d69d7167-00d1-49c5-90ee-6bc0b7e8295f@kernel.org>
On 11/23/25 15:57, Christophe Leroy (CS GROUP) wrote:
>
>
> Le 23/11/2025 à 13:13, René Rebe a écrit :
>> Building a size optimized ppc64 kernel (-Os), gcc emits more FP
>> save/restore symbols, that the linker generates on demand into the
>> .sfpr section. Explicitly allow-list those in scripts/mod/modpost.c,
>> too. They are needed for the amdgpu in-kernel floating point support.
>
> Would have been interested to know with which version of GCC the problem
> started.
I can reproduce the modpost errors on GCC 15.2 and GCC 11.5.
Same kernel .config builds ok with CLANG 20.1.8 however.
> By the way you seem to fix the problem for modules, but does it also
> work when amdgpu is in kernel ? I would have expected a need to add
> functions in arch/powerpc/lib/crtsavres.S as well, just like following
> commits:
If I build amdgpu statically into the kernel I don't get the modpost
errors, the build finishes successfully. Only building amdgpu as module
leads to these errors Rene reported.
Regards,
Erhard
prev parent reply other threads:[~2025-11-26 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-23 12:13 [PATCH V2] modpost: Amend ppc64 save/restfpr symnames for -Os build René Rebe
2025-11-23 14:57 ` Christophe Leroy (CS GROUP)
2025-11-23 15:09 ` René Rebe
2025-11-23 15:25 ` René Rebe
2025-11-26 0:16 ` Erhard Furtner [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=7e955a64-2fe6-4b8e-b49e-c3f827029b2b@mailbox.org \
--to=erhard_f@mailbox.org \
--cc=chleroy@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=rene@exactco.de \
/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).