This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [4.0.x] may reach end warning in system headers
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Michael Veksler <VEKSLER at il dot ibm dot com>
- Cc: Geoff Keating <geoffk at apple dot com>, pinskia at physics dot uc dot edu, gcc-patches at gcc dot gnu dot org
- Date: 02 Jul 2005 14:50:21 +0200
- Subject: Re: [4.0.x] may reach end warning in system headers
- References: <OF9479086D.FBE10BD6-ONC2257032.002B2B71-C2257032.0040C5A0@il.ibm.com>
Michael Veksler <VEKSLER@il.ibm.com> writes:
| References: <20050701183024.E138714C16A9@geoffk5.apple.com> <
| 2f5a1d4159b3d47bfd0842beeaa06f3e@physics.uc.edu>
|
| Geoff Keating wrote:
| > On 01/07/2005, at 11:32 AM, Andrew Pinski wrote:
| > > This is PR 21951 which should be worked around in
| > > libstdc++ instead of in GCC or at that least that
| > > is what was decided.
| >
| >
| > It's wrong that the compiler is warning about a system
| > header, even if libstdc++ should be changed to fix this
| > one instance.
|
| I agree with this view for a production compiler only
| (on a release branch). I don't agree with this view for
| the trunk.
| Enabling warnings in system headers should be done at
| the same time as checking is enabled for gcc
| (configure --enable-checking), otherwise bugs in system
| headers might escape.
yes, but in this specific case, I don't see a bug in libstdc++ headers.
-- Gaby