Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: RFA: don't try to compare IEEE NaN's
Date: Wed, 06 Jun 2001 15:08:00 -0000	[thread overview]
Message-ID: <npy9r52rcn.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <3B1E6E7A.CEBC4116@cygnus.com>

Michael Snyder <msnyder@cygnus.com> writes:
> BTW, the reason for using a union as I did, rather than individual
> char, short, int etc. variables, was to make sure that the known bit
> pattern was actually larger than the type being tested -- so that we
> would know if, for instance, GDB was testing more bits than it
> should.

I don't think my patch breaks this property.  After I write to
testval.float_testval, the subsequent bytes are still 0xff.  And if a
double is no smaller than a float, it works for the double test, too.

If we're trying to catch more-bits-than-appropriate comparisons,
shouldn't the *_resultval variables be in a union with a distinct
background pattern, too?  Say, zeros?


  parent reply	other threads:[~2001-06-06 15:08 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 [this message]
2001-06-06 23:19           ` Eli Zaretskii
2001-06-06 23:19         ` Eli Zaretskii
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=npy9r52rcn.fsf@zwingli.cygnus.com \
    --to=jimb@zwingli.cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.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