From: David Edelsohn <dje.gcc@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Musl libm optimizations for Power and Z
Date: Wed, 17 May 2017 13:05:31 -0400 [thread overview]
Message-ID: <CAGWvnyko_PQcULY4iT2UNxDoDqnYqppazLtieiLuxeN8sb0o5A@mail.gmail.com> (raw)
In-Reply-To: <20170517163342.GI17319@brightrain.aerifal.cx>
On Wed, May 17, 2017 at 12:33 PM, Rich Felker <dalias@libc.org> wrote:
> On Wed, May 17, 2017 at 10:52:05AM -0400, David Edelsohn wrote:
>> On Wed, May 17, 2017 at 10:26 AM, Szabolcs Nagy <nsz@port70.net> wrote:
>> > * David Edelsohn <dje.gcc@gmail.com> [2017-05-17 09:49:22 -0400]:
>> >> Are there any musl developers who would be interested to work on musl
>> >> libm optimizations for Power and Z as financial bounties?
>> >
>> > i hope it is something upstreamable
>> > (i'm interested in libm optimizations, but cant work for bounties)
>>
>> I'm not certain what you mean. We want musl libm to include
>> optimizations for Power and Z in the musl repository and releases.
>
> Upstreamability could include 2 things: both your/contributor's
> willingness to submit the code upstream, and appropriateness of it for
> inclusion.
>
> In general we avoid having per-arch math code that's more than simple
> fpu instruction wrappers -- math/i386/*.s is about the upper bound on
> what I have in mind, as opposed to something like using an entirely
> different C algorithm that just happens to be faster on the arch or
> that only tangentially uses arch-specific insns. And more importantly,
> arch-specific math asm should not be sacrificing correctness/quality
> of results for performance or other considerations.
The Power and Z ports deserve the same math instruction optimizations
as x86 and ARM.
Thanks, David
next prev parent reply other threads:[~2017-05-17 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 13:49 David Edelsohn
2017-05-17 14:26 ` Szabolcs Nagy
2017-05-17 14:52 ` David Edelsohn
2017-05-17 16:33 ` Rich Felker
2017-05-17 17:05 ` David Edelsohn [this message]
2017-05-17 17:17 ` Rich Felker
2017-05-18 16:31 ` David Edelsohn
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=CAGWvnyko_PQcULY4iT2UNxDoDqnYqppazLtieiLuxeN8sb0o5A@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).