Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: will.newton@linaro.org
Cc: gdb-patches@sourceware.org, patches@linaro.org
Subject: Re: [PATCH 2/2] gdb/doublest.c: Use frexpl rather than ldfrexp.
Date: Fri, 14 Jun 2013 13:03:00 -0000	[thread overview]
Message-ID: <201306141252.r5ECqxUX021717@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <51BB0DAE.2070504@linaro.org> (message from Will Newton on Fri,	14 Jun 2013 13:33:50 +0100)

> Date: Fri, 14 Jun 2013 13:33:50 +0100
> From: Will Newton <will.newton@linaro.org>
> 
> Most modern systems have frexpl and gnulib provides an implementation
> for those that don't, so use it instead of the generic but inaccurate
> ldfrexp.

Great!  Hopefully somebody with more gnulib experience can approve the
other diff.

> gdb/ChangeLog:
> 
> 2013-06-14  Will Newton  <will.newton@linaro.org>
> 
> 	* doublest.c (ldfrexp): Remove function.
> 	(convert_doublest_to_floatformat): Call frexpl instead of
> 	ldfrexp.
> ---
>  gdb/doublest.c | 49 +------------------------------------------------
>  1 file changed, 1 insertion(+), 48 deletions(-)
> 
> diff --git a/gdb/doublest.c b/gdb/doublest.c
> index 9ddc7a6..2e4c87e 100644
> --- a/gdb/doublest.c
> +++ b/gdb/doublest.c
> @@ -336,53 +336,6 @@ put_field (unsigned char *data, enum floatformat_byteorders order,
>      }
>  }
> 
> -#ifdef HAVE_LONG_DOUBLE
> -/* Return the fractional part of VALUE, and put the exponent of VALUE in *EPTR.
> -   The range of the returned value is >= 0.5 and < 1.0.  This is equivalent to
> -   frexp, but operates on the long double data type.  */
> -
> -static long double ldfrexp (long double value, int *eptr);
> -
> -static long double
> -ldfrexp (long double value, int *eptr)
> -{
> -  long double tmp;
> -  int exp;
> -
> -  /* Unfortunately, there are no portable functions for extracting the
> -     exponent of a long double, so we have to do it iteratively by
> -     multiplying or dividing by two until the fraction is between 0.5
> -     and 1.0.  */
> -
> -  if (value < 0.0l)
> -    value = -value;
> -
> -  tmp = 1.0l;
> -  exp = 0;
> -
> -  if (value >= tmp)		/* Value >= 1.0 */
> -    while (value >= tmp)
> -      {
> -	tmp *= 2.0l;
> -	exp++;
> -      }
> -  else if (value != 0.0l)	/* Value < 1.0  and > 0.0 */
> -    {
> -      while (value < tmp)
> -	{
> -	  tmp /= 2.0l;
> -	  exp--;
> -	}
> -      tmp *= 2.0l;
> -      exp++;
> -    }
> -
> -  *eptr = exp;
> -  return value / tmp;
> -}
> -#endif /* HAVE_LONG_DOUBLE */
> -
> -
>  /* The converse: convert the DOUBLEST *FROM to an extended float and
>     store where TO points.  Neither FROM nor TO have any alignment
>     restrictions.  */
> @@ -466,7 +419,7 @@ convert_doublest_to_floatformat (CONST struct floatformat *fmt,
>      }
> 
>  #ifdef HAVE_LONG_DOUBLE
> -  mant = ldfrexp (dfrom, &exponent);
> +  mant = frexpl (dfrom, &exponent);
>  #else
>    mant = frexp (dfrom, &exponent);
>  #endif
> -- 
> 1.8.1.4
> 
> 


  reply	other threads:[~2013-06-14 12:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14 12:34 Will Newton
2013-06-14 13:03 ` Mark Kettenis [this message]
2013-06-21 10:58 ` Will Newton
2013-06-21 16:28 ` Joel Brobecker
2013-06-21 16:44   ` Will Newton

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=201306141252.r5ECqxUX021717@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --cc=patches@linaro.org \
    --cc=will.newton@linaro.org \
    /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