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: Add a __nowarn__ keyword


On Thu, 9 Aug 2007, Mark Mitchell wrote:

> DJ Delorie wrote:
>
> > If we can solve a subset of the attachment problem, let's use the
> > push/pop technique I described.  It sets us up for all the things
> > we'll need if/when we solve the general attachment problem.
>
> I think we should add the push/pop, and then accept that it's not
> perfect yet.  It's still better than nothing, and it would probably work
> well for many front-end warnings, which is where most warnings come from.
> Mark Mitchell

Based on the above, and on Ian's comments regarding warnings from the
middle-end, I think we're going to extend the pragma interface rather than
accept __nowarn__.  In this case I think DJ or someone familiar with that
code is better suited to implement the push/pop mechiansim than I.

I made a good-faith effort to provide a way for users to "elegantly" work
around -Wcast-qual warnings as Mark requested.  Since we're not going to
use it and the existing mechanism doesn't work yet, what I'd like to do is
install my CONST_CAST patch using the union.  When the pragma interface is
suitably updated, I volunteer to update the definition of CONST_CAST in
system.h to take advantage of it.  Meanwhile I can finish the
constification stuff and get GCC bootstrapping with -Wcast-qual enabled.

Mark - okay to install CONST_CAST using a union?
http://gcc.gnu.org/ml/gcc-patches/2007-07/msg01993.html

		Thanks,
		--Kaveh
--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu


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