This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: fixes for type-punning warnings in GCC 4.1
- From: Daniel Jacobowitz <drow at false dot org>
- To: Alexandre Oliva <aoliva at redhat dot com>
- Cc: Eli Zaretskii <eliz at gnu dot org>, gdb-patches at sources dot redhat dot com
- Date: Tue, 7 Feb 2006 23:59:05 -0500
- Subject: Re: fixes for type-punning warnings in GCC 4.1
- References: <ork6e0nban.fsf@livre.oliva.athome.lsd.ic.unicamp.br> <ufyoog2mf.fsf@gnu.org> <20051219221830.GA32448@nevyn.them.org> <or1wz8gham.fsf@livre.oliva.athome.lsd.ic.unicamp.br> <20060122203323.GC27224@nevyn.them.org> <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