This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: Wno-warning-directives [WasRe: cpplib: Start moving ...]
Richard Henderson <rth@redhat.com>
>
> On Mon, Aug 12, 2002 at 04:41:10PM -0700, Stan Shebs wrote:
> > Sure, it was handy to see the #warning the first time, but it's
> > unreasonable to expect everyone to stop using -Werror until all
> > the #warnings are removed.
>
> Why? That's what -Werror is *for* -- to prevent you
> from ignoring warnings. If that's not what you want,
> don't use it.
And if you WANT to catch the -Wuninitialized warnings with an error, but
you do NOT want to be stopped by the idiot /usr/include/foo.h that puts
a #warning into their .h file for no good reason?
The -Werror hammer is often too coarse grained with all of the possible
warnings that can be generated during a build. Until and unless we can
more selectively turn off 'warnings' the -Werror switch will continue to
be a pain to use.
-- Mark