From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: libm
Date: Mon, 5 Mar 2012 16:17:11 +0100 [thread overview]
Message-ID: <20120305151710.GG5728@port70.net> (raw)
In-Reply-To: <20120305140459.GW184@brightrain.aerifal.cx>
* Rich Felker <dalias@aerifal.cx> [2012-03-05 09:04:59 -0500]:
> On Mon, Mar 05, 2012 at 09:51:35AM +0100, Szabolcs Nagy wrote:
> Hm? If you need a macro to test whether an argument is an integer or
> floating point, try this:
>
> #define __IS_FP(x) !!((1?1:(x))/2)
>
oh nice
(and subtle)
> I can do it, but might be another day or two. Feel free to keep fixing
> stuff up in the mean time if you have time. :)
>
ok
> > i saw that you removed the compound literal definition of
> > NAN, INFINITY etc from math.h
> >
>
> The removal has nothing to do with c89; it's actually the fact that
> the compound literal definition was not a constant expression and the
> standard requires these macros to expand to constant expressions.
>
i see
> adopted it. In any case I see no good way to define them without
> compound literals except the function calls..
>
btw while testing these macros i noticed that when
multiple classification macros are used fpclassify
gets called many times
(with the previous solution)
the extra calls could be optimized by adding
__attribute__((const)) to fpclassify
(resulted less calls, smaller code size etc)
> > hm but float compare will compile to different instruction
> > so there is at least performance difference
>
> Yes. In principle it would be faster to do everything as floating
> point so no store/load delays are needed. In relality I doubt it makes
> much of a difference. In almost all of these functions the actual
> computation time dominates.
>
i see
next prev parent reply other threads:[~2012-03-05 15:17 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 ` libm Szabolcs Nagy
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 ` Szabolcs Nagy [this message]
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=20120305151710.GG5728@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).