linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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:02:07 -0600	[thread overview]
Message-ID: <20240212170207.GW19790@gate.crashing.org> (raw)
In-Reply-To: <995988479.14839534.1707756078600.JavaMail.zimbra@raptorengineeringinc.com>

On Mon, Feb 12, 2024 at 10:41:18AM -0600, Timothy Pearson wrote:
> Implement gpr1 and fpu save/restore functions per the ABI v2 documentation.

There is no "ABI v2".  This is the ELFv2 ABI, it is a name, it is not a
version 2 of anything (in fact, it is version 1 everywhere).

The same functions are needed and used in other ABIs, too.

But, why do this patch?  You just need

+LIBGCC         := $(shell $(CC) $(KBUILD_CFLAGS) -print-libgcc-file-name)

+libs-y += $(LIBGCC)

and nothing more.  It is required for proper functioning of GCC to link
with the libgcc support library.


Segher

  reply	other threads:[~2024-02-12 17:03 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 [this message]
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
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=20240212170207.GW19790@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).