From: Carlo Wood <carlo@alinoe.com>
To: Ian Lance Taylor <ian@wasabisystems.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com
Subject: Re: RFA: Support infinity, NaN, and denormalized numbers in floatformat.c
Date: Wed, 03 Dec 2003 18:57:00 -0000 [thread overview]
Message-ID: <20031203185657.GA30735@alinoe.com> (raw)
In-Reply-To: <m3iskxbv1v.fsf@gossamer.airs.com>
On Wed, Dec 03, 2003 at 01:44:28PM -0500, Ian Lance Taylor wrote:
> literal, I can use the floatformat structures to pull it apart. I
> then plan to output the literal as a C99 hex floating point constant.
> (A couple of people suggested this approach, and I can't think of a
> good reason to not do it.)
I think they meant to use C99 hex as the base for a new mangling,
and then print that more or less literally when demangling. That would
avoid rounding on both ends (I understood that C99 corresponds exactly
with the internal representation of floats by gcc anyway) and removes all
target dependency. I disagree with this, but well - its not that important.
[...]
> This approach probably doesn't help you, since you probably don't want
> to deal with the floatformat routines.
They allocate memory - therefore prefer to simply output the mangled bit.
After all,...
[...]
> I do think this is all kind of ridiculous, since I'm sure that nobody
> uses floating point constants in template expressions in real life.
Exactly what I've said several times :/. I think my last patch is my
last word in the subject of demangling floats. I'll have another look
iff a third party files a real-life complaint through GNATS, and not
sooner.
Thanks for your reply,
Carlo
next prev parent reply other threads:[~2003-12-03 18:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 18:12 Ian Lance Taylor
2003-12-03 18:17 ` Daniel Jacobowitz
2003-12-03 19:09 ` Andrew Cagney
2003-12-03 18:35 ` Carlo Wood
2003-12-03 18:44 ` Ian Lance Taylor
2003-12-03 18:57 ` Carlo Wood [this message]
2003-12-03 18:35 ` DJ Delorie
2003-12-03 18:47 ` Paul Koning
2012-08-16 16:20 ` Andreas Schwab
2012-08-17 21:16 ` Ian Lance Taylor
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=20031203185657.GA30735@alinoe.com \
--to=carlo@alinoe.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ian@wasabisystems.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