This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PATCH: Wno-warning-directives [WasRe: cpplib: Start moving ...]


"Mark D. Baushke" <mdb@gnu.org> writes:

> 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 solution we usually recommend for this is to use sed or grep on
the compiler's output.  Various solutions have been proposed to
integrate that functionality into the compiler, but no-one has yet
wanted it badly enough to implement any of them.

-- 
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]