From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Dodgy functions (finitel, strold)
Date: Tue, 29 Mar 2016 16:09:00 -0000 [thread overview]
Message-ID: <20160326194047.GD8327@calimero.vinschen.de> (raw)
In-Reply-To: <CAJ1FpuO8p2NNERWzXWuahiz91_27_TA3RUP=xJ=UzZZVY1YZVw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]
On Mar 25 18:16, Doug Henderson wrote:
> On 25 March 2016 at 02:59, Achim Gratz <Stromeko@nexgo.de> wrote:
> >
> > Achim Gratz writes:
> > > Achim Gratz writes:
> > >> Long story short, they seem to report a finite value on at least some
> > >> NaN constructs and then the %a format for the Perl sprintf outputs those
> > >> bits as a hex FP number rather than just printing "NaN". On 64bit the
> > >> culprit is actually finitel, of course, since Perl gets compiled with
> > >> long doubles.
> > >
> > > And looking into newlib this seems to be a compile bug, because the
> > > function just uses an intrinsic.
> >
> > But the compiler is innocent, because newlib uses the wrong intrinsic or
> > an incomplete implementation. If it must be using that intrinsic for
> > compatibility reasons, it would need to implement
> >
> > <snip>
> >
> > Regards,
> > Achim.
> >
>
>
> I modified your program to display the actual hex value of the a, b,
> and c variables. The b and c variables have different bit patterns. It
> appears that the %a format conversion is (correctly) detecting ±inf
> and NaN according to IEEE 754, and ignoring the value of all other
> bits in the variables.
>
> It appears that strtold and the implicit conversion from double to
> long double are setting some of the bits which are not used to
> represent NaN or ±Inf to different values.
strtold actually forgot to set one bit.
I now fixed finitel, the return value of strtold for +/-infinity,
and I improved math.h by using GCC builtins for the C99 macros
which makes them type agnostic and thus lon double aware.
Building a snaphot right now. Please give it a try.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-26 19:41 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.20160318203409.GA11113@calimero.vinschen.de>
[not found] ` <56EC6BDA.7050505@cornell.edu>
2016-03-18 21:45 ` [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.8 Corinna Vinschen
2016-03-18 22:25 ` Ken Brown
2016-03-18 22:40 ` Ken Brown
2016-03-18 23:05 ` Yaakov Selkowitz
2016-03-18 23:29 ` Yaakov Selkowitz
2016-03-19 2:24 ` Ken Brown
2016-03-19 10:32 ` Corinna Vinschen
2016-03-19 12:34 ` Ken Brown
2016-03-19 18:03 ` Ken Brown
2016-03-20 15:26 ` Corinna Vinschen
2016-03-20 19:27 ` Ken Brown
2016-03-20 19:40 ` Ken Brown
2016-03-20 20:18 ` Ken Brown
2016-03-20 20:47 ` Yaakov Selkowitz
2016-03-21 14:13 ` Ken Brown
2016-03-21 16:30 ` Corinna Vinschen
2016-03-21 17:59 ` Ken Brown
2016-03-22 11:15 ` Corinna Vinschen
2016-03-22 14:59 ` Ken Brown
2016-03-30 21:17 ` Corinna Vinschen
2016-03-31 11:55 ` Ken Brown
2016-03-20 4:50 ` Yaakov Selkowitz
2016-03-20 15:18 ` Corinna Vinschen
2016-03-20 10:59 ` Achim Gratz
2016-03-20 11:14 ` Marco Atzeri
2016-03-20 15:25 ` Corinna Vinschen
2016-03-20 19:27 ` Achim Gratz
2016-03-20 20:53 ` Corinna Vinschen
2016-03-20 21:30 ` Corinna Vinschen
2016-03-20 20:24 ` Achim Gratz
2016-03-20 20:45 ` Yaakov Selkowitz
2016-03-22 9:31 ` Achim Gratz
2016-03-25 9:00 ` Dodgy functions (was: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.8) Achim Gratz
2016-03-26 0:16 ` Dodgy functions Achim Gratz
2016-03-26 19:41 ` Dodgy functions (finitel, strold) Achim Gratz
2016-03-29 16:09 ` Doug Henderson
2016-03-29 16:09 ` Corinna Vinschen [this message]
2016-04-01 19:04 ` Achim Gratz
2016-03-22 17:43 ` [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.8 Chris Sutcliffe
2016-03-22 18:02 ` Corinna Vinschen
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=20160326194047.GD8327@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@cygwin.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).