From: Steven Munroe <munroesj@linux.vnet.ibm.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] powerpc: Add a POWER8-optimized version of powf()
Date: Sat, 27 May 2017 00:38:00 -0000 [thread overview]
Message-ID: <1495845477.31269.11.camel@oc7878010663> (raw)
In-Reply-To: <9d5740ea-fb29-13d9-b71c-de29290350aa@linaro.org>
On Fri, 2017-05-26 at 16:55 -0300, Adhemerval Zanella wrote:
>
> On 25/05/2017 14:47, Paul Clarke wrote:
> > This implementation is heavily based on sysdeps/ieee754/flt-32/e_powf.c.
> > Most significant changes are code simplification and use of doubles for
> > intermediate values. Also, some rearrangement to move early
> > non-dependent code later, out of the faster paths.
> >
> > 2017-05-25 Paul A. Clarke <pc@us.ibm.com>
> >
> > * sysdeps/powerpc/powerpc64/fpu/multiarch/Makefile
> > [$(subdir) = math] (libm-sysdep_routines): Add e_powf-power8 and
> > e_powf-ppc64.
> > * sysdeps/powerpc/powerpc64/fpu/multiarch/e_powf-power8.c: New file.
> > * sysdeps/powerpc/powerpc64/fpu/multiarch/e_powf-ppc64.c: Likewise.
> > * sysdeps/powerpc/powerpc64/fpu/multiarch/e_powf.c: Likewise.
> > * sysdeps/powerpc/powerpc64/power8/fpu/e_powf.c: Likewise.
>
> This changes seems to be arch independent and I would like to avoid adding
> even more arch specific. Is there any reason why this can't be used as
> the default implementation? Do you have number on different architecture
> for it?
>
If other platform maintainer what to try this implementation and report
that would be OK.
But I don't this it is correct or fair to ask Paul to prove a negative.
These quests tend to be very labor intensive and usually don't work out
(as really common) in the end.
next prev parent reply other threads:[~2017-05-27 0:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 17:47 Paul Clarke
2017-05-26 19:55 ` Adhemerval Zanella
2017-05-27 0:38 ` Steven Munroe [this message]
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
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=1495845477.31269.11.camel@oc7878010663 \
--to=munroesj@linux.vnet.ibm.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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).