From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: aoliva@redhat.com
Cc: eliz@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: fixes for type-punning warnings in GCC 4.1
Date: Mon, 13 Feb 2006 20:13:00 -0000 [thread overview]
Message-ID: <200602132013.k1DKDLH8031169@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <oraccvgk87.fsf@free.oliva.athome.lsd.ic.unicamp.br> (message from Alexandre Oliva on Mon, 13 Feb 2006 16:57:28 -0200)
> From: Alexandre Oliva <aoliva@redhat.com>
> Date: Mon, 13 Feb 2006 16:57:28 -0200
>
> Ok to install?
Looks ok to me.
> for gdb/ChangeLog
> from Alexandre Oliva <aoliva@redhat.com>
>
> * doublest.h (DOUBLEST): Use long double only if we can scan
> it in. Undefine HAVE_LONG_DOUBLE otherwise.
> (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.
> * varobj.c (free_variable): Silence type-punning warnings.
> * tui/tui-data.h (struct tui_list): Change type of list member.
> * tui/tui-data.c: Remove no-longer-needed type casts.
> (source_windows): Silence type-punning warnings.
> * tui/tui-stack.c, tui/tui-win.c, tui/tui-winsource.c: Likewise.
next prev parent reply other threads:[~2006-02-13 20:13 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 [this message]
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=200602132013.k1DKDLH8031169@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--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