From: "Keith Packard" <keithp@keithp.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>, newlib@sourceware.org
Subject: Re: [PATCH 0/3] ARM with only 32-bit floats do not have fast 64-bit FMA
Date: Mon, 10 Aug 2020 08:19:34 -0700 [thread overview]
Message-ID: <87eeoev88p.fsf@keithp.com> (raw)
In-Reply-To: <20200810144316.GM14398@arm.com>
[-- Attachment #1: Type: text/plain, Size: 248 bytes --]
Szabolcs Nagy <szabolcs.nagy@arm.com> writes:
> but using HAVE_FAST_FMA{F} works too.
> (note that these macros currently only
> do something useful on aarch64 and arm.)
I've got a patch for RISC-V FMA support in the works.
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-08-10 15:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 22:34 Keith Packard
2020-08-08 22:34 ` [PATCH 1/3] libm: ARM without HW double does not have fast FMA Keith Packard
2020-08-08 22:34 ` [PATCH 2/3] libm: Detect fast fmaf support Keith Packard
2020-08-08 22:34 ` [PATCH 3/3] libm/machine/arm: Add optimized fmaf and fma when available Keith Packard
2020-08-10 9:30 ` [PATCH 0/3] ARM with only 32-bit floats do not have fast 64-bit FMA Corinna Vinschen
2020-08-10 14:43 ` Szabolcs Nagy
2020-08-10 15:19 ` Keith Packard [this message]
2020-08-10 19:06 ` Corinna Vinschen
2020-09-01 16:32 ` Sebastian Huber
2020-09-01 17:21 ` Sebastian Huber
2020-09-01 18:04 ` Sebastian Huber
2020-09-01 19:28 ` Keith Packard
2020-09-01 21:16 ` Joseph Myers
2020-09-01 23:06 ` Keith Packard
2020-09-02 4:41 ` Sebastian Huber
2020-09-02 5:25 ` Keith Packard
2020-09-02 5:35 ` Keith Packard
2020-09-02 17:12 ` Joseph Myers
2020-09-02 17:59 ` Sebastian Huber
2020-09-02 20:39 ` Keith Packard
2020-09-01 19:50 ` Keith Packard
2020-09-07 14:09 Eric Bresie
2020-09-07 17:16 ` Keith Packard
2020-09-07 20:16 ` Brian Inglis
2020-09-07 22:23 ` Keith Packard
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=87eeoev88p.fsf@keithp.com \
--to=keithp@keithp.com \
--cc=newlib@sourceware.org \
--cc=szabolcs.nagy@arm.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).