From: Andrew Cagney <ac131313@cygnus.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc/rfa] Almost eliminate HOST_{FLOAT,DOUBLE,...}_FORMAT
Date: Wed, 04 Jul 2001 12:24:00 -0000 [thread overview]
Message-ID: <3B436D73.3060908@cygnus.com> (raw)
In-Reply-To: <1010629204858.ZM13994@ocotillo.lan>
> On Jun 29, 1:23pm, Andrew Cagney wrote:
>
>
>> This patch changes GDB so that, if the host configury didn't specify the
>> floating point format, it will fall back immediatly to floatformat_*().
>> Previously, GDB would assume that the HOST had IEEE FP and try to use
>> that.
>>
>> For hosts that don't specify a HOST_*_FORMAT, this will mean a loss of
>> FP precision when using GDB :-/
>
>
> Are you suggesting that hosts should define HOST_*_FORMAT? Or should
> we attempt to eliminate the HOST_*_FORMAT macros entirely?
I think we should eliminate HOST_*_FORMAT entirely. GDB should always
use something like ``sim/common/sim-fpu.[hc]'' to do its FP emulation.
that way, no matter what the host/target, GDB provides both consistent
and exact FP behavour.
Andrew
prev parent reply other threads:[~2001-07-04 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B3CB989.1000706@cygnus.com>
2001-06-29 13:49 ` Kevin Buettner
2001-06-29 15:20 ` Kevin Buettner
2001-07-04 12:24 ` 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=3B436D73.3060908@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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