From: Joseph Myers <joseph@codesourcery.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Umesh Kalappa <umesh.kalappa0@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
<linuxppc-dev@lists.ozlabs.org>, <gcc@gcc.gnu.org>,
<libc-alpha@sourceware.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Paul E Murphy <murphyp@linux.ibm.com>
Subject: Re: Passing the complex args in the GPR's
Date: Tue, 6 Jun 2023 17:18:47 +0000 [thread overview]
Message-ID: <c3e887b3-7c98-22b9-75d8-39edd7631d3@codesourcery.com> (raw)
In-Reply-To: <CA+=Sn1=gt-nf4T3vfWDKQLRNKkuBXh98nLbTtiCGDSPhMxyRiQ@mail.gmail.com>
On Tue, 6 Jun 2023, Andrew Pinski via Gcc wrote:
> You are looking at the wrong ABI document.
> That is for the 64bit ABI.
> The 32bit ABI document is located at:
> http://refspecs.linux-foundation.org/elf/elfspec_ppc.pdf
>
> Plus the 32bit ABI document does not document Complex argument passing
> as it was written in 1995 and never updated.
For the 32-bit ABI see
https://www.polyomino.org.uk/publications/2011/Power-Arch-32-bit-ABI-supp-1.0-Unified.pdf
(sources at https://github.com/ryanarn/powerabi - power.org has long since
disappeared).
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2023-06-06 17:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 9:38 [PATCH Linux] powerpc: add documentation for HWCAPs Nicholas Piggin
2022-05-24 9:52 ` Florian Weimer
2022-05-24 18:32 ` Segher Boessenkool
2022-07-15 1:17 ` Nicholas Piggin
2022-07-15 14:35 ` Segher Boessenkool
2022-05-24 17:38 ` Segher Boessenkool
2022-07-15 1:00 ` Nicholas Piggin
2023-06-06 14:49 ` Passing the complex args in the GPR's Umesh Kalappa
2023-06-06 14:58 ` Andrew Pinski
2023-06-06 15:05 ` Umesh Kalappa
2023-06-06 15:16 ` Andrew Pinski
2023-06-06 16:42 ` Segher Boessenkool
2023-06-06 17:07 ` Umesh Kalappa
2023-06-06 17:33 ` David Edelsohn
2023-06-07 13:17 ` Michael Matz
2023-06-06 17:18 ` Joseph Myers [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=c3e887b3-7c98-22b9-75d8-39edd7631d3@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=murphyp@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=pinskia@gmail.com \
--cc=segher@kernel.crashing.org \
--cc=umesh.kalappa0@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).