Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: dgm69@us.ibm.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Have gdb display float infinity.
Date: Mon, 22 Aug 2005 20:28:00 -0000	[thread overview]
Message-ID: <200508221955.j7MJtcP0019867@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <Pine.WNT.4.63.0508221353540.2128@dwayne> (message from Dwayne Grant McConnell on Mon, 22 Aug 2005 14:00:11 -0500 (Central Daylight Time))

> Date: Mon, 22 Aug 2005 14:00:11 -0500 (Central Daylight Time)
> From: Dwayne Grant McConnell <dgm69@us.ibm.com>
> 
> I noticed that gdb does display NaNs in a special way but not infinity. 
> This patch changes that. I'm a bit new here so I have a few questions.

Thanks!  Since you're new, I'll have to ask whether you have a
copyright assignment for gdb?

> 1. Should I submit a testcase to go along with the patch? as a separate 
> patch? (I have no idea were to put it yet but I figured I would ask.)

Yes please!  A seperate patch is fine, but make sure it gets in
shortly before or after the fix gets in.

> 2. I simply duplicated floatformat_is_nan() with one minor change to 
> produce floatformat_is_inf(). I could have done this differently. Should I 
> have changed float_format_is_nan() to float_format_is_nan_or_inf() and 
> given the function a parameter for NaN v Inf? Something else?

Hmm, this indeeds seems to duplicate a fair amount of code.  Having
seperate functions for nan and inf is good I think, but do you see a
way to avoid code duplication?

> I have tested this with both ppc and ppc64 but nothing else.

It'd be great if you also could test this on another platform,
preferably amd64, i386 or m68k since those have extended double
formats.

Mark


  reply	other threads:[~2005-08-22 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22 19:38 Dwayne Grant McConnell
2005-08-22 20:28 ` Mark Kettenis [this message]
2005-08-22 21:42   ` Dwayne Grant McConnell

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=200508221955.j7MJtcP0019867@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=dgm69@us.ibm.com \
    --cc=gdb-patches@sources.redhat.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