unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek via Libc-alpha <libc-alpha@sourceware.org>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
	Jacob Lifshay <programmerjake@gmail.com>,
	llvm-dev <llvm-dev@lists.llvm.org>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	IA32 System V Application Binary Interface
	<ia32-abi@googlegroups.com>,
	Joseph Myers <joseph@codesourcery.com>
Subject: Re: [llvm-dev] [PATCH] Add optional _Float16 support
Date: Fri, 2 Jul 2021 11:21:33 +0200	[thread overview]
Message-ID: <20210702092133.GI7746@tucnak> (raw)
In-Reply-To: <CAFiYyc2-1Qpb=xas9hAk1KFcYGgEY8S+ENbBrcc_L-OrQvh83g@mail.gmail.com>

On Fri, Jul 02, 2021 at 09:45:46AM +0200, Richard Biener via Gcc-patches wrote:
> > > > are?  (If it is restricted to SSE, we can of course ensure relevant
> > > libgcc
> > > > functions are built with SSE enabled, and likewise in glibc if that gains
> > > > _Float16 functions, though maybe with some extra complications to get
> > > > relevant testcases to run whenever possible.)
> > > >
> > >
> > > _Float16 functions in libgcc should be compiled with SSE enabled.
> > >
> > > 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.
> > >
> >
> > Umm, if you just need to load/store 16-bit scalars in XMM registers you can
> > use pextrw and pinsrw which don't require AVX. f16x8 can use any of the
> > standard full-register load/stores.
> 
> It looks like that requires SSE2, with SSE only inserts/extracts
> to/from MMX regs
> are supported.  But of course GPR half-word loads and GPR->XMM moves of
> full size would work.

Loads can be done in SSE2 directly with PINSRW, that supports 16-bit load
from memory to XMM reg.  But SSE2 PEXTRW only supports stores into GPR
and one needs SSE4.1 fo PEXTRW into memory.  So, for the stores and SSE2 one
needs secondary reload...

	Jakub


  parent reply	other threads:[~2021-07-02  9:22 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 [this message]
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=20210702092133.GI7746@tucnak \
    --to=libc-alpha@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ia32-abi@googlegroups.com \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=llvm-dev@lists.llvm.org \
    --cc=programmerjake@gmail.com \
    --cc=richard.guenther@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).