mailing list of musl libc
 help / color / mirror / code / Atom feed
From: enh <enh@google.com>
To: enh <enh@google.com>,
	musl@lists.openwall.com, vincenzo.innocente@cern.ch,
	 riemannic@gmail.com
Subject: Re: [musl] Accuracy of Mathematical Functions
Date: Fri, 22 Sep 2023 11:04:08 -0700	[thread overview]
Message-ID: <CAJgzZorRPaBn9BZZMMDmf7vU-+p64BBfzJQwOvKpN6WEdATwWg@mail.gmail.com> (raw)
In-Reply-To: <20230922064410.GB1427497@port70.net>

oh, interesting... i see a lot of the files in the arm directory have
freebsd in the name but, yes, even there the majority seems to be
home-grown code.

On Thu, Sep 21, 2023 at 11:44 PM Szabolcs Nagy <nsz@port70.net> wrote:
>
> * enh <enh@google.com> [2023-09-21 09:30:10 -0700]:
> > isn't Apple's libm (like Android's) largely the FreeBSD libm? are the
> > Apple vs FreeBSD differences you found really FreeBSD/arm64 vs
> > FreeBSD/x86-64 differences? (or differences between older and newer
> > FreeBSD libms?)
>
> freebsd is mostly c so behaves the same on x86 and arm
> (fma usage can be different but that's about it)
>
> in the apple libm neither x86 nor arm version looks freebsd based
> (and this is old, they likely updated it for aarch64)
>
> https://opensource.apple.com/source/Libm/Libm-2026/Source/
>

  reply	other threads:[~2023-09-22 18:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21  7:30 Paul Zimmermann
2023-09-21 16:30 ` enh
2023-09-22  6:44   ` Szabolcs Nagy
2023-09-22 18:04     ` enh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-15 15:00 Paul Zimmermann
2023-02-14  8:16 Paul Zimmermann
2022-08-29 10:59 Paul Zimmermann
2021-09-07 15:02 [musl] accuracy of mathematical functions Paul Zimmermann
2021-08-03  8:36 Paul Zimmermann
2021-08-03 12:56 ` Morten Welinder
2021-02-05 10:48 Paul Zimmermann

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=CAJgzZorRPaBn9BZZMMDmf7vU-+p64BBfzJQwOvKpN6WEdATwWg@mail.gmail.com \
    --to=enh@google.com \
    --cc=musl@lists.openwall.com \
    --cc=riemannic@gmail.com \
    --cc=vincenzo.innocente@cern.ch \
    /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).