From: Segher Boessenkool <segher@kernel.crashing.org>
To: Timothy Pearson <tpearson@raptorengineering.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc: Add gpr1 and fpu save/restore functions
Date: Mon, 12 Feb 2024 11:59:06 -0600 [thread overview]
Message-ID: <20240212175906.GY19790@gate.crashing.org> (raw)
In-Reply-To: <572013249.14851324.1707759979044.JavaMail.zimbra@raptorengineeringinc.com>
On Mon, Feb 12, 2024 at 11:46:19AM -0600, Timothy Pearson wrote:
> Interesting, that make sense.
>
> How should we proceed from the current situation? Bringing in libgcc seems
> like a fairly invasive change,
I have done it for *all* architectures some ten years ago. Never found
any problem.
> should we merge this to fix the current bug
> (cannot build ppc64 kernel in size-optimized mode) and start discussion on
> bringing in libgcc as the long-term fix across multiple architectures?
>
> My goal here is to not have to carry a downstream patch in perpetuity for
> our embedded Linux firmware, which needs to be compiled in size-optimized
> mode due to hardware Flash limitations.
There are better options than -Os, fwiw. Some --param's give smaller
*and* faster kernels. What exactly is best is heavily arch-dependent
though (as well as dependent on the application code, the kernel code in
this case) :-(
Segher
next prev parent reply other threads:[~2024-02-12 18:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 16:41 [PATCH] powerpc: Add gpr1 and fpu save/restore functions Timothy Pearson
2024-02-12 17:02 ` Segher Boessenkool
2024-02-12 17:09 ` Timothy Pearson
2024-02-12 17:30 ` Segher Boessenkool
2024-02-12 17:46 ` Timothy Pearson
2024-02-12 17:59 ` Segher Boessenkool [this message]
2024-02-12 18:07 ` Timothy Pearson
2024-02-12 18:23 ` Segher Boessenkool
2024-02-12 18:31 ` Timothy Pearson
2024-02-13 5:23 ` Michael Ellerman
2024-02-13 5:28 ` Timothy Pearson
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=20240212175906.GY19790@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tpearson@raptorengineering.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;
as well as URLs for NNTP newsgroup(s).