mailing list of musl libc
 help / color / mirror / code / Atom feed
From: ardi <ardillasdelmonte@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Feasability of patching libm with OS X 10.5.8 libc for IBM double-double in PPC
Date: Wed, 6 Dec 2017 20:33:54 +0100	[thread overview]
Message-ID: <CA+fZqCWZFeB1bNj+pV8B1AKw0od9m9NJyNvd6bd-M7fE++ks5Q@mail.gmail.com> (raw)
In-Reply-To: <20171206175333.GC15263@port70.net>

On Wed, Dec 6, 2017 at 6:53 PM, Szabolcs Nagy <nsz@port70.net> wrote:
> * ardi <ardillasdelmonte@gmail.com> [2017-12-06 18:23:33 +0100]:
>> Said this, I need IBM double-double in PowerPC targets (using clang as
>> compiler), and I'd like to use musl because of its well written code.
>
> is this because of some abi compat issue?
> or some source code depends on double-double semantics?

It's because I have code that was very well tuned for double-double
precision. Of course I'd be happy to be able to work with an IEEE
128bit long double, and I'd use it from the first day if the LLVM
compiler team implements it with hardware optimizations for PPC64, but
I'd like to have the choice of using double-double if I need to check
or compare at some point.

From the comments by Rich, I think maybe it's not hard to get it
working. If I find I can get it by patching a few files (maybe
conditionally using the code for FP to/from string conversions in
Apple libc in my custom musl build), then I'll do it. OTOH, if it
requires a lot of editing, I won't doing it, because I want to have an
easy procedure for updating musl to newer versions. If I have to apply
a huge patchset whenever I update, it wouldn't be reasonable.

Thanks!


      reply	other threads:[~2017-12-06 19:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 17:23 ardi
2017-12-06 17:33 ` Rich Felker
2017-12-06 17:53 ` Szabolcs Nagy
2017-12-06 19:33   ` ardi [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+fZqCWZFeB1bNj+pV8B1AKw0od9m9NJyNvd6bd-M7fE++ks5Q@mail.gmail.com \
    --to=ardillasdelmonte@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).