From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: libm
Date: Mon, 27 Feb 2012 22:02:53 +0100 [thread overview]
Message-ID: <20120227210253.GA25004@port70.net> (raw)
In-Reply-To: <20120123170715.GA197@brightrain.aerifal.cx>
* Rich Felker <dalias@aerifal.cx> [2012-01-23 12:07:15 -0500]:
> On Mon, Jan 23, 2012 at 05:41:52PM +0100, Szabolcs Nagy wrote:
> > i've looked into libm implementations
> > to figure out what's best for musl
>
> > the extended precision algorithms are reused across
...
>
> Any ideas how the different ones evolved (separately written or common
> ancestor code, etc.) and where we should look to pull code from?
>
meanwhile i looked more into libm design issues
here are some questions i come up with:
for background issues see
http://nsz.repo.hu/libm
Code organization:
(ldX is X bit long double)
Do we want ld128?
Should we try to use common code for ld80 and ld128?
How to do ld64: wrap double functions or alias them?
How to tie the ld* code to the arch in the build system?
Make complex optional?
Keep complex in math/ or cmath/?
Workarounds:
Use STDC pragmas (eventhough gcc does not support them)?
Use volatile consistently to avoid evaluation precision and const folding issues?
Use special compiler flags against unwanted optimization (-frounding-math, -ffloat-store)?
Do inline/macro optimization for small functions? (isnan, isinf, signbit, creal, cimag,..)
In complex code prefer creal(), cimag() or a union to (un)pack re,im?
Code cleanups:
Keep diffability with freebsd/openbsd code or reformat the code for clarity?
Keep e_, s_, k_ fdlibm source file name prefixes?
Should 0x1p0 float format be preferred over decimal format?
Should isnan, signbit,.. be preferred over inplace bithacks?
Is unpacking a double into 2 int32_t ok (signed int representation)?
Is unpacking the mantissa of ld80 into an int64_t ok?
next prev parent reply other threads:[~2012-02-27 21:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 16:41 libm Szabolcs Nagy
2012-01-23 17:07 ` libm Rich Felker
2012-01-23 19:12 ` libm Szabolcs Nagy
2012-01-27 16:02 ` libm Szabolcs Nagy
2012-01-27 19:01 ` libm Pascal Cuoq
2012-01-27 19:34 ` libm Rich Felker
2012-01-29 16:34 ` libm Szabolcs Nagy
2012-02-27 21:02 ` Szabolcs Nagy [this message]
2012-02-27 22:24 ` libm Rich Felker
2012-03-03 22:57 ` libm Szabolcs Nagy
2012-03-04 6:53 ` libm Rich Felker
2012-03-04 14:50 ` libm Szabolcs Nagy
2012-03-04 18:43 ` libm Rich Felker
2012-03-05 8:51 ` libm Szabolcs Nagy
2012-03-05 14:04 ` libm Rich Felker
2012-03-05 15:17 ` libm Szabolcs Nagy
2012-03-05 15:25 ` libm Rich Felker
2012-03-09 10:22 ` libm Rich Felker
2012-03-09 10:57 ` libm Szabolcs Nagy
2012-03-09 16:01 ` libm Rich Felker
2012-03-09 11:09 ` libm Szabolcs Nagy
2012-03-09 15:56 ` libm Rich Felker
2012-03-09 17:02 ` libm Rich Felker
2012-03-10 3:28 ` libm Rich Felker
2012-03-10 12:45 ` libm Szabolcs Nagy
2012-03-10 13:12 ` libm Rich Felker
2012-03-10 16:38 ` libm Szabolcs Nagy
2012-03-05 11:08 ` libm Szabolcs Nagy
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=20120227210253.GA25004@port70.net \
--to=nsz@port70.net \
--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).