From: Will Newton <will.newton@linaro.org>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Patch Tracking <patches@linaro.org>
Subject: Re: [PATCH 2/2] gdb/doublest.c: Use frexpl rather than ldfrexp.
Date: Fri, 21 Jun 2013 10:58:00 -0000 [thread overview]
Message-ID: <CANu=DmiVZB6Dx8dKb5sYLd3SL8Gj4vN-MpXu8LwovbwK-h4OvA@mail.gmail.com> (raw)
In-Reply-To: <51BB0DAE.2070504@linaro.org>
On 14 June 2013 13:33, Will Newton <will.newton@linaro.org> wrote:
>
> 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.
>
> 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(-)
Ping?
--
Will Newton
Toolchain Working Group, Linaro
next prev parent reply other threads:[~2013-06-21 10:58 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
2013-06-21 10:58 ` Will Newton [this message]
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='CANu=DmiVZB6Dx8dKb5sYLd3SL8Gj4vN-MpXu8LwovbwK-h4OvA@mail.gmail.com' \
--to=will.newton@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=patches@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