From: Joseph Myers <joseph@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: llvm-dev@lists.llvm.org, GCC Patches <gcc-patches@gcc.gnu.org>,
GNU C Library <libc-alpha@sourceware.org>,
IA32 System V Application Binary Interface
<ia32-abi@googlegroups.com>
Subject: Re: [PATCH] Add optional _Float16 support
Date: Thu, 1 Jul 2021 22:40:16 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2107012233420.419529@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAMe9rOo8vgANgSuxJjvt5A98TL9Hz1SQc7mk3gDnz7gX=Uk+KA@mail.gmail.com>
On Thu, 1 Jul 2021, H.J. Lu wrote:
> BTW, _Float16 software emulation may require more than just SSE
> since we need to do _Float16 load and store with XMM registers.
> There is no 16bit load/store for XMM registers without AVX512FP16.
You should be able to make the move go via general-purpose registers (for
example) if you can't do a direct 16-bit load/store for XMM registers.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-07-01 22:40 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 [this message]
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
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.2107012233420.419529@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=ia32-abi@googlegroups.com \
--cc=libc-alpha@sourceware.org \
--cc=llvm-dev@lists.llvm.org \
/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).