This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [RFC] Backport -Wstrict-aliasing warnings for C++ to 4.1
- From: Richard Guenther <rguenther at suse dot de>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org, mark at codesourcery dot com, libstdc++ at gcc dot gnu dot org
- Date: Wed, 7 Dec 2005 16:42:27 +0100 (CET)
- Subject: Re: [RFC] Backport -Wstrict-aliasing warnings for C++ to 4.1
- References: <Pine.LNX.4.63.0512071631550.6048@t148.fhfr.qr> <20051207153800.GP31785@devserv.devel.redhat.com>
On Wed, 7 Dec 2005, Jakub Jelinek wrote:
> On Wed, Dec 07, 2005 at 04:34:55PM +0100, Richard Guenther wrote:
> >
> > Is it ok to backport the following two patches from mainline to
> > gcc 4.1? All the libstdc++ changes regarding to the change have
> > already been backported to 4.1.
>
> Even the
> 2005-11-23 Paolo Carlini <pcarlini@suse.de>
>
> PR libstdc++/24975 (basic_string)
> * include/bits/basic_string.h (_Rep::_S_empty_rep): Avoid
> strict-aliasing warnings.
>
> change? I don't see it on gcc-4_1-branch...
Ah no - that's missing and we appearantly have that patched in our
distributions compiler together with the warning. So - ok to backport
the warning bits together with this workaround?
Richard.