From: Joseph Myers <joseph@codesourcery.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: "munroesj@linux.vnet.ibm.com" <munroesj@linux.vnet.ibm.com>,
"adhemerval.zanella@linaro.org" <adhemerval.zanella@linaro.org>,
"pc@us.ibm.com" <pc@us.ibm.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [PATCH] powerpc: Add a POWER8-optimized version of powf()
Date: Fri, 02 Jun 2017 16:28:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1706021623420.29125@digraph.polyomino.org.uk> (raw)
In-Reply-To: <AM5PR0802MB2610F743AF2A1DDEAC176B1E83F70@AM5PR0802MB2610.eurprd08.prod.outlook.com>
On Fri, 2 Jun 2017, Wilco Dijkstra wrote:
> >> As it happens Szabolcs wrote a prototype powf that is not only more
> >> accurate but also 4x faster, all using generic code. With these
> >> gains, target specific math functions will be obsolete...
> >
> > Is that forthcoming?
>
> Yes - after they are published under a less restrictive license. In
> GLIBC we'll need to agree on how to deal with the wrappers and establish
> a good place to add new math functions.
It's fine to put float functions implemented using double internally in
sysdeps/ieee754/flt-32; some already use double internally. For functions
not using type-generic templates, the sysdeps/ieee754 structure seems
reasonable to me (given the need to handle different long double formats),
although code outside there may also assume that float is binary32 and
double is binary64.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-06-02 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 12:55 Wilco Dijkstra
2017-05-30 17:03 ` Paul Clarke
2017-06-02 16:06 ` Wilco Dijkstra
2017-06-02 16:28 ` Joseph Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-25 17:47 Paul Clarke
2017-05-26 19:55 ` Adhemerval Zanella
2017-05-27 0:38 ` Steven Munroe
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=alpine.DEB.2.20.1706021623420.29125@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=munroesj@linux.vnet.ibm.com \
--cc=nd@arm.com \
--cc=pc@us.ibm.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).