OK, I see your point. it would take really long to find out you are
using the wrong isnan.
I guess I could provide an inline implementation using the builtin.
most of libm is type-generic, though I guess isinf/isnan are the ones
people actually use as such.
On Wed, Feb 14, 2018 at 01:49:45PM +, co...@sdf.org wrote:
> Hi,
>
> we produce suboptimal code because e.g. isinf and isnan are namespace
> guarded, we define a __isnan instead, and use macros to rename.
> this disallows compilers from optimizing the function with a builtin,
> which saves at
Hi,
we produce suboptimal code because e.g. isinf and isnan are namespace
guarded, we define a __isnan instead, and use macros to rename.
this disallows compilers from optimizing the function with a builtin,
which saves at least the function call.
can we as a policy have symbols for all the stand
