From: Mark Kettenis <kettenis@wins.uva.nl>
To: ac131313@cygnus.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] New function to convert floating-point types
Date: Mon, 29 Oct 2001 15:43:00 -0000 [thread overview]
Message-ID: <200110292343.f9TNh8L17592@delius.kettenis.local> (raw)
In-Reply-To: <3BDDBA24.10803@cygnus.com>
Date: Mon, 29 Oct 2001 15:20:52 -0500
From: Andrew Cagney <ac131313@cygnus.com>
> Any objections to checking this in?
Not from me.
So I went ahead and committed it :-)
--
This prodded me to think about what DOUBLEST should be changed to. Up
until now I'd been thinking of some sort of generic floating point type.
However, looking at your case suggests instead something like:
struct doublest
{
char value[a-large-number];
const struct floatformat *format;
};
Convert to DOUBLEST would just leave the format as-is. Only when a
conversion was really needed would it be converted.
Hmm. I see DOUBLEST as a host-specific thing. In the ideal case
target-dependent code wouldn't need DOUBLEST at all.
Mark
next prev parent reply other threads:[~2001-10-29 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-28 15:44 Mark Kettenis
2001-10-29 12:21 ` Andrew Cagney
2001-10-29 15:43 ` Mark Kettenis [this message]
2001-10-29 16:54 ` Andrew Cagney
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=200110292343.f9TNh8L17592@delius.kettenis.local \
--to=kettenis@wins.uva.nl \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.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