From: Daniel Jacobowitz <drow@false.org>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: fixes for type-punning warnings in GCC 4.1
Date: Wed, 08 Feb 2006 04:59:00 -0000 [thread overview]
Message-ID: <20060208045905.GA12327@nevyn.them.org> (raw)
In-Reply-To: <oru0bazhuc.fsf@livre.oliva.athome.lsd.ic.unicamp.br>
On Wed, Feb 08, 2006 at 12:48:11AM -0200, Alexandre Oliva wrote:
> On Jan 22, 2006, Daniel Jacobowitz <drow@false.org> wrote:
>
> > The output is always a DOUBLEST. I don't know of any reason why we
> > should enable HAVE_LONG_DOUBLE if we can't printf and scanf them; would
> > this be simpler in that case? Don't make DOUBLEST something we can't
> > scan or print.
>
> Sounds good to me. Ok to install?
Well, it's not right as-is; you need to look at the other uses of
HAVE_LONG_DOUBLE. It's not obviously harmful, but the long double
support code in doublest.c should match the condition on
DOUBLEST-is-long-double.
Would you mind terribly fixing that, adding a changelog, and leaving
out the tui-data change for now? Anything that needs an explanatory
paragraph it's probably worth seeing how hard the interface fix is;
if you don't have time, I'll do it.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-08 4:59 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 [this message]
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
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=20060208045905.GA12327@nevyn.them.org \
--to=drow@false.org \
--cc=aoliva@redhat.com \
--cc=eliz@gnu.org \
--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