This is the mail archive of the gcc@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: named warnings & individual warning control

From: Mark Mitchell <mark at codesourcery dot com>
To: DJ Delorie <dj at redhat dot com>
Cc: gcc at gcc dot gnu dot org
Date: Wed, 30 Jun 2004 19:06:56 -0700
Subject: Re: named warnings & individual warning control
Organization: CodeSourcery, LLC
References: <200406211908.i5LJ8mCX027121@greed.delorie.com> <40D7CF2B.2030405@codesourcery.com> <200406221400.i5ME0QjE002663@greed.delorie.com> <40D85A29.9070503@codesourcery.com> <200406221714.i5MHEM6i005590@greed.delorie.com> <40D86E05.8070805@codesourcery.com> <200406221850.i5MIo2S0007045@greed.delorie.com> <40D88578.6080306@codesourcery.com> <200406242210.i5OMAwbp023722@greed.delorie.com> <40DBB1D7.6070108@codesourcery.com> <200406282056.i5SKu4oL029790@greed.delorie.com>

If we keep track of the input_location info with the warning control
state, we can get around this problem.  Then we'd also not need the
API for obtaining the warning state and keeping track of it.

That's a good idea.

Summary:

I think this is a good plan, and not controversial.

Thanks for working it out.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

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