From: Andrew Cagney <ac131313@cygnus.com>
To: Mark Kettenis <kettenis@wins.uva.nl>
Cc: gdb-patches@sources.redhat.com, gdb@sources.redhat.com,
taylor@cygnus.com
Subject: Re: [PATCH, RFA]: Revamp NaN detection & discussion
Date: Wed, 21 Mar 2001 06:40:00 -0000 [thread overview]
Message-ID: <3AB8B4FE.1A7F7C9@cygnus.com> (raw)
In-Reply-To: <200101252103.f0PL3ig00326@delius.kettenis.local>
> I also have an itch about floatformat.{ch} and its functions. I'd
> rather put all floatformat_* functions in there rather than in
> defs.h/utils.c. But since it's part of libiberty that's a bit of a
> pain. Is this stuff really used anywhere outside GDB? If not,
> perhaps we could claim it back. Otherwise I'd like to add a
> gdb_floatformat.{ch} and put all the floatformat stuff there.
Hmm, looked in the TODO file? (I'll append all the comments).
Given that no one appears to be using floatformat (unless GCC is?) I
think we can ``claim it back''.
At a more idealistic level we could instead use sim/common/sim-fpu.[ch]
and implement GDB's target floating point using that. I can but dream
:-)
Andrew
PS: The harris mess is sorted out - harris is obsolete.
--
Rationalize use of floatformat_unknown in GDB sources.
Instead of defaulting to floatformat_unknown, should hosts/targets
specify the value explicitly?
http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00447.html
--
Add a ``name'' member to include/floatformat.h:struct floatformat.
Print that name in gdbarch.c.
--
Sort out the harris mess in include/floatformat.h (it hardwires two
different floating point formats).
--
See of the GDB local floatformat_do_doublest() and libiberty's
floatformat_to_double (which was once GDB's ...) can be merged some
how.
--
Deprecate current use of ``floatformat_unknown''.
Require all targets to explicitly provide their float format instead
of defaulting to floatformat unknown. Doing the latter leads to nasty
bugs.
http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00447.html
--
Rationalize floatformat_to_double() vs floatformat_to_doublest().
Looks like GDB migrated floatformat_to_double() to libiberty but then
turned around and created a ..._to_doublest() the latter containing
several bug fixes.
http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00472.html
--
Move floatformat_ia64_ext to libiberty/include floatformat.[ch].
http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00466.html
--
prev parent reply other threads:[~2001-03-21 6:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 13:03 Mark Kettenis
2001-03-21 6:40 ` Andrew Cagney [this message]
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=3AB8B4FE.1A7F7C9@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@wins.uva.nl \
--cc=taylor@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