From: Eli Zaretskii <eliz@is.elta.co.il>
To: Jim Blandy <jimb@zwingli.cygnus.com>
Cc: Jim Blandy <jimb@cygnus.com>,
gdb-patches@sources.redhat.com, msnyder@cygnus.com
Subject: Re: RFA: don't try to compare IEEE NaN's
Date: Wed, 06 Jun 2001 23:19:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010607091954.28343B-100000@is> (raw)
In-Reply-To: <npn17l4ife.fsf@zwingli.cygnus.com>
On 6 Jun 2001, Jim Blandy wrote:
> What you're saying is that, between this:
>
> union {
> float f;
> char bytes[80];
> } u;
>
> for (i = 0; i < 80; i++)
> u.bytes[i] = something interesting;
>
> and this:
>
> u.f = 2.7182818284590452354;
>
> that you're more concerned that the latter will put a NaN in u.f than
> the former.
Yes.
> When, in fact, the exact problem I'm trying to fix is
> that someone's first shot at the former strategy produced a NaN.
That's because the bit pattern used by the original code was a bit
pattern of a NaN in the first place. In other words, we've got
exactly what we were asking for. You cannot expect that with a
literal FP constant like the one you used.
next prev parent reply other threads:[~2001-06-06 23:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 20:40 Jim Blandy
2001-06-05 23:14 ` Eli Zaretskii
2001-06-06 6:54 ` Fernando Nasser
2001-06-06 7:27 ` Jim Blandy
2001-06-06 8:46 ` Eli Zaretskii
2001-06-06 9:15 ` Fernando Nasser
2001-06-06 11:38 ` Jim Blandy
2001-06-06 11:52 ` Fernando Nasser
2001-06-06 13:59 ` Michael Snyder
2001-06-06 23:20 ` Eli Zaretskii
2001-06-06 23:19 ` Eli Zaretskii
2001-06-06 10:37 ` Jim Blandy
2001-06-06 10:55 ` Michael Snyder
2001-06-06 11:04 ` Fernando Nasser
2001-06-06 11:15 ` Michael Snyder
2001-06-06 15:08 ` Jim Blandy
2001-06-06 23:19 ` Eli Zaretskii
2001-06-06 23:19 ` Eli Zaretskii [this message]
2001-06-07 10:38 ` Michael Snyder
2001-06-07 11:38 ` Eli Zaretskii
2001-06-06 13:17 ` Michael Meissner
2001-06-06 13:45 ` Fernando Nasser
2001-06-06 23:21 ` Eli Zaretskii
2001-06-06 6:45 ` Fernando Nasser
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=Pine.SUN.3.91.1010607091954.28343B-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@cygnus.com \
--cc=jimb@zwingli.cygnus.com \
--cc=msnyder@cygnus.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