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: Alexandre Oliva <aoliva at redhat dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Wed, 08 Feb 2006 03:58:01 -0200
- 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 Feb 8, 2006, Alexandre Oliva <aoliva@redhat.com> 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?
GRR. quilt was eating my ChangeLog entries :-( Here's what I meant to
post along with the previous patch:
for gdb/ChangeLog
from Alexandre Oliva <aoliva@redhat.com>
* doublest.h (DOUBLEST): Use long double only if we can scan in.
(DOUBLEST_FORMAT): New.
* c-exp.y (parse_number): Use it.
* jv-exp.y (parse_number): Likewise.
* objc-exp.y (parse_number): Likewise.
* p-exp.y (parse_number): Likewise.
* tui/tui-data.c (source_windows): Silence type-punning warnings.
* varobj.c (free_variable): Likewise.
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
Secretary for FSF Latin America http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}