From: Joseph Myers <joseph@codesourcery.com>
To: IA32 System V Application Binary Interface <ia32-abi@googlegroups.com>
Cc: "Wang, Pengfei" <pengfei.wang@intel.com>,
llvm-dev@lists.llvm.org,
GNU C Library <libc-alpha@sourceware.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [llvm-dev] [PATCH] Add optional _Float16 support
Date: Tue, 13 Jul 2021 15:41:08 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2107131536460.2044871@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAMe9rOppeyatAtdj--hJmiNdinTx7UO7vOAsKVqY5Xv5dfLFMA@mail.gmail.com>
On Tue, 13 Jul 2021, H.J. Lu wrote:
> On Mon, Jul 12, 2021 at 8:59 PM Wang, Pengfei <pengfei.wang@intel.com> wrote:
> >
> > > Return _Float16 and _Complex _Float16 values in %xmm0/%xmm1 registers.
> >
> > Can you please explain the behavior here? Is there difference between _Float16 and _Complex _Float16 when return? I.e.,
> > 1, In which case will _Float16 values return in both %xmm0 and %xmm1?
> > 2, For a single _Float16 value, are both real part and imaginary part returned in %xmm0? Or returned in %xmm0 and %xmm1 respectively?
>
> Here is the v2 patch to add the missing _Float16 bits. The PDF file is at
>
> https://gitlab.com/x86-psABIs/i386-ABI/-/wikis/Intel386-psABI
This PDF shows _Complex _Float16 as having a size of 2 bytes (should be
4-byte size, 2-byte alignment).
It also seems to change double from 4-byte to 8-byte alignment, which is
wrong. And it's inconsistent about whether it covers the long double =
double (Android) case - it shows that case for _Complex long double but
not for long double itself.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-07-13 15:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 21:05 [PATCH] Add optional _Float16 support H.J. Lu via Libc-alpha
2021-07-01 22:10 ` Joseph Myers
2021-07-01 22:27 ` H.J. Lu via Libc-alpha
2021-07-01 22:40 ` Joseph Myers
2021-07-01 23:01 ` H.J. Lu via Libc-alpha
2021-07-01 23:05 ` [llvm-dev] " Craig Topper via Libc-alpha
2021-07-01 23:33 ` Jacob Lifshay via Libc-alpha
2021-07-02 7:45 ` Richard Biener via Libc-alpha
2021-07-02 8:03 ` Hongtao Liu via Libc-alpha
2021-07-02 9:21 ` Jakub Jelinek via Libc-alpha
2021-07-13 3:59 ` Wang, Pengfei via Libc-alpha
2021-07-13 14:26 ` H.J. Lu via Libc-alpha
2021-07-13 14:48 ` Wang, Pengfei via Libc-alpha
2021-07-13 15:04 ` H.J. Lu via Libc-alpha
2021-07-13 15:41 ` Joseph Myers [this message]
2021-07-13 16:24 ` H.J. Lu via Libc-alpha
2021-07-29 13:39 ` H.J. Lu via Libc-alpha
2021-08-24 5:55 ` John McCall via Libc-alpha
2021-08-25 12:35 ` H.J. Lu via Libc-alpha
2021-08-25 20:32 ` John McCall via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.22.394.2107131536460.2044871@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ia32-abi@googlegroups.com \
--cc=libc-alpha@sourceware.org \
--cc=llvm-dev@lists.llvm.org \
--cc=pengfei.wang@intel.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).