From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Alan Modra <amodra@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: IBM long double little-endian
Date: Tue, 20 Aug 2013 06:45:00 -0000 [thread overview]
Message-ID: <20130820064459.GA28832@host2.jankratochvil.net> (raw)
In-Reply-To: <20130819003948.GM4024@bubble.grove.modra.org>
Hello Alan,
just a ping to get it fixed ASAP:
On Mon, 19 Aug 2013 02:39:48 +0200, Alan Modra wrote:
> include/
> * floatformat.h (floatformat_ibm_long_double): Delete.
> (floatformat_ibm_long_double_big): Declare.
> (floatformat_ibm_long_double_little): Declare.
>
> libiberty/
> * floatformat.c (floatformat_ibm_long_double): Rename to..
> (floatformat_ibm_long_double_big): ..this.
> (floatformat_ibm_long_double_little): New.
This part is now checked in the GDB repository with:
commit 4f5b788afee21f1333c3acc207b4940af960f6da
Author: DJ Delorie <dj@delorie.com>
Date: Tue Aug 20 06:02:49 2013 +0000
merge from gcc
> gdb/
> * doublest.c (convert_floatformat_to_doublest): Use fmt->split_half
> for IBM long double nan and inf.
> (floatformat_is_negative, floatformat_classify,
> floatformat_mantissa): Similarly.
> (floatformat_ieee_single, floatformat_ieee_double,
> floatformat_ieee_quad, floatformat_arm_ext,
> floatformat_ia64_spill): Delete unused vars.
> (_initialize_doublest): Delete unused function.
> * gdbtypes.c (floatformats_ibm_long_double): Use new big- and
> little-endian variants of floatformat_ibm_long_double.
so this part should be checked in now due to:
gdbtypes.c:111:4: error: 'floatformat_ibm_long_double' undeclared here (not in a function)
Thanks,
Jan
next prev parent reply other threads:[~2013-08-20 6:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 0:39 Alan Modra
2013-08-19 7:33 ` Andreas Schwab
2013-08-19 15:53 ` Tom Tromey
2013-08-20 6:45 ` Jan Kratochvil [this message]
2013-08-20 6:49 ` Alan Modra
2013-08-20 17:52 ` DJ Delorie
2013-08-20 22:46 ` Alan Modra
2013-08-21 4:05 ` Tom Tromey
2013-08-21 7:24 ` Andreas Schwab
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=20130820064459.GA28832@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=amodra@gmail.com \
--cc=gdb-patches@sourceware.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