From: Andrew Pinski <pinskia@gmail.com>
To: Umesh Kalappa <umesh.kalappa0@gmail.com>
Cc: 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 07:58:05 -0700 [thread overview]
Message-ID: <CA+=Sn1=gt-nf4T3vfWDKQLRNKkuBXh98nLbTtiCGDSPhMxyRiQ@mail.gmail.com> (raw)
In-Reply-To: <CAGfacvTu_8tZnndLqbRJeU4UJrnq+tCchiZyFFqOE-hXM0=wCA@mail.gmail.com>
On Tue, Jun 6, 2023 at 7:50 AM Umesh Kalappa via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> Hi all ,
>
> For the test case https://godbolt.org/z/vjs1vfs5W ,we see the mismatch
> in the ABI b/w gcc and clang .
>
> Do we have any supporting documents that second the GCC behaviour over CLANG ?
>
> EABI states like
>
> In the Power Architecture 64-Bit ELF V2 ABI Specification document
> (v1.1 from 16 July 2015)
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.
https://www.nxp.com/docs/en/reference-manual/E500ABIUG.pdf does not
document it either.
Thanks,
Andrew Pinski
>
> Page 53:
>
> Map complex floating-point and complex integer types as if the
> argument was specified as separate real
> and imaginary parts.
>
> and in this case the double complexes are broken down with double real
> and double img and expected to pass in FPR not the GPR.
>
>
>
> Thank you
> ~Umesh
next prev parent reply other threads:[~2023-06-06 14:58 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 [this message]
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
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='CA+=Sn1=gt-nf4T3vfWDKQLRNKkuBXh98nLbTtiCGDSPhMxyRiQ@mail.gmail.com' \
--to=pinskia@gmail.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=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).