mailing list of musl libc
 help / color / mirror / code / Atom feed
From: enh <enh@google.com>
To: musl@lists.openwall.com
Cc: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Subject: Re: [musl] Re: integration of CORE-MATH routines into Musl?
Date: Fri, 2 Sep 2022 12:28:33 -0700	[thread overview]
Message-ID: <CAJgzZopFT85iJ5nKZuOAGOW05utTNGcwOjY_tZOUoc_mtXMMXg@mail.gmail.com> (raw)
In-Reply-To: <20220902121755.GS7074@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 2527 bytes --]

On Fri, Sep 2, 2022 at 5:18 AM Rich Felker <dalias@libc.org> wrote:

> On Fri, Sep 02, 2022 at 12:10:18PM +0200, Paul Zimmermann wrote:
> >        Dear Rich,
> >
> > we now distribute the CORE-MATH routines under the MIT license,
> > to ease integration into Musl (among other libraries).
> >
> > Please can you point out to a Musl developer who might be
> > interested to integrate some CORE-MATH routines?
> >
> > We will try to answer potential issues that might arise
> > during this integration.
> >
> > Best regards,
> > Paul
> >
> > PS: see https://hal.inria.fr/hal-03721525 for more details about
> > the CORE-MATH project.
>
> Could you summaraize briefly what you have in mind, and what tradeoffs
> might be? Are these intended to be drop-in replacements for the
> existing standard functions, or implementations for the "cr" versions
> thereof? I have not followed closely the "mandatory requirement of
> correct rounding for mathematical functions in the next revision of
> the IEEE-754 standard" topic and how it relates to the future of C,
> but my vague recollection was that the direction folks were leaning
> was towards a separate set of cr*() functions or something. But if
> it's possible to do correct rounding in a way that's all-wins
> (performance, size, quality of results) or nearly all wins (maybe
> slightly larger?), at least for select functions, that seems very
> interesting.
>

"what he said" (including the "i haven't been following the details").

assuming you have good answers to those questions then -- if you haven't
already done so -- you should probably also bring this up with
freebsd-numerics (https://wiki.freebsd.org/Numerics and the mailing list
mentioned on that page). that's the source of the vast majority of the libm
code used by Android/iOS/macOS. (the exceptions for Android are mostly
binary128 stuff from netbsd and arm32/arm64 optimized code from
https://github.com/ARM-software/optimized-routines.)

on the opposite end of the spectrum, llvm-libc isn't widely used at all,
but that work is at such an early stage (although it seems like they have
had a heavy libm focus) that they probably don't have existing
implementations for a lot of stuff.

it seems -- having admittedly not read past the abstract of the paper that
you linked to -- that you're only addressing binary32 so far? not even
binary64? (i'm used to binary128 not getting much love!)

(oh, and thanks for picking a license that makes it much more likely that
all the libcs can use your work!)


> Rich
>

[-- Attachment #2: Type: text/html, Size: 3511 bytes --]

  reply	other threads:[~2022-09-02 19:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mwv8q6ccj9.fsf@tomate.loria.fr>
2022-09-02 12:17 ` Rich Felker
2022-09-02 19:28   ` enh [this message]
2022-09-02 20:40     ` enh
2022-09-05  9:09   ` Paul Zimmermann
2022-09-05 13:08     ` Szabolcs Nagy
2022-09-05 14:39       ` Paul Zimmermann
2022-09-05 16:38         ` Szabolcs Nagy
2022-09-06 23:40     ` enh

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=CAJgzZopFT85iJ5nKZuOAGOW05utTNGcwOjY_tZOUoc_mtXMMXg@mail.gmail.com \
    --to=enh@google.com \
    --cc=Paul.Zimmermann@inria.fr \
    --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).