From: Daniel Jacobowitz <drow@false.org>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: fixes for type-punning warnings in GCC 4.1
Date: Mon, 13 Feb 2006 20:19:00 -0000 [thread overview]
Message-ID: <20060213201952.GA1888@nevyn.them.org> (raw)
In-Reply-To: <200602132013.k1DKDLH8031169@elgar.sibelius.xs4all.nl> <oraccvgk87.fsf@free.oliva.athome.lsd.ic.unicamp.br>
On Mon, Feb 13, 2006 at 04:57:28PM -0200, Alexandre Oliva wrote:
> Yep. It didn't look like those two occurrences were such a big deal.
> I don't see why we should refuse to handle long double at all just
> because we can't scan them in as such. But it's not my call, I guess.
My only point here was that, if we know that DOUBLEST is a double,
then casting it to a long double and passing it to a home-brewed
long double reimplementation of ldexp is pretty silly; the other
HAVE_LONG_DOUBLE conditionals were all really
"DOUBLEST_IS_LONG_DOUBLE".
On Mon, Feb 13, 2006 at 09:13:21PM +0100, Mark Kettenis wrote:
> > From: Alexandre Oliva <aoliva@redhat.com>
> > Date: Mon, 13 Feb 2006 16:57:28 -0200
> >
> > Ok to install?
>
> Looks ok to me.
Me too. Thanks!
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-13 20:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 19:35 Alexandre Oliva
2005-12-20 20:50 ` Eli Zaretskii
2005-12-20 21:05 ` Daniel Jacobowitz
2005-12-21 11:25 ` Eli Zaretskii
2005-12-22 3:48 ` Alexandre Oliva
2006-01-16 18:27 ` Alexandre Oliva
2006-01-22 20:33 ` Daniel Jacobowitz
2006-02-08 3:35 ` Alexandre Oliva
2006-02-08 4:59 ` Daniel Jacobowitz
2006-02-10 0:33 ` Alexandre Oliva
2006-02-10 1:39 ` Daniel Jacobowitz
2006-02-13 18:58 ` Alexandre Oliva
2006-02-13 20:13 ` Mark Kettenis
2006-02-13 20:19 ` Daniel Jacobowitz [this message]
2006-02-08 5:58 ` Alexandre Oliva
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=20060213201952.GA1888@nevyn.them.org \
--to=drow@false.org \
--cc=aoliva@redhat.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