From: Shawn Landden <slandden@gmail.com>
To: GT <tnggil@protonmail.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] powerpc: add libmvec implementations of log and logf
Date: Fri, 17 May 2019 09:59:09 -0500 [thread overview]
Message-ID: <CA+49okrw+PsS45vcXYRC7KkkXgqWsRim+Fp4dg2m-NJ16wbe+A@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1905071516230.3445@digraph.polyomino.org.uk>
Hi,
On Tue, May 7, 2019 at 10:21 AM Joseph Myers <joseph@codesourcery.com> wrote:
>
> Since you and Bert Tenjy have now posted rival patch versions implementing
> vector log, a key performance comparison would be against the version
> posted by Bert Tenjy
> <https://sourceware.org/ml/libc-alpha/2019-05/msg00054.html> - and in
> general, you should compare and contrast the two versions of log to
> justify why one might be better than another. It's also important in such
> cases to be very clear about where exactly the patch you are posting fits
> into exactly what other patch series.
Bert,
Are you working on pow/powf?
Shawn
prev parent reply other threads:[~2019-05-17 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 20:34 [RFC][PATCH] powerpc: add libmvec implementations of log and logf Shawn Landden
2019-05-05 20:53 ` Shawn Landden
2019-05-06 20:32 ` [PATCH] " Shawn Landden
2019-05-07 15:21 ` Joseph Myers
2019-05-08 23:04 ` Shawn Landden
2019-05-09 19:58 ` Tulio Magno Quites Machado Filho
2019-05-10 1:00 ` Shawn Landden
2019-05-10 19:16 ` Tulio Magno Quites Machado Filho
2019-05-13 16:50 ` Joseph Myers
2019-05-13 21:28 ` Shawn Landden
2019-05-17 14:59 ` Shawn Landden [this message]
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=CA+49okrw+PsS45vcXYRC7KkkXgqWsRim+Fp4dg2m-NJ16wbe+A@mail.gmail.com \
--to=slandden@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=tnggil@protonmail.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).