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]

Re: "introduce no new bootstrap warning" criteria. was: Loop iv debugging patch


On 15-Jan-2001, Philipp Thomas <pthomas@suse.de> wrote:
> #pragma GCC warning push
> #pragma GCC warning unused off
> <some code>
> #pragma GCC warning pop.

That's very prolix syntax.  It would be quite unfortunate if you have to
write three #pragmas just to disable one warning.

I'd much prefer something more similar to the current `__extension__'.
For example `__nowarn__', used as a prefix on an expression,
declaration, or statement, could disable all warnings for just that
expression/declaration/statement.  Alternatively,
`__disablewarn__(NAME)' could be used in the same contexts to
selectively disable specific warnings.

-- 
Fergus Henderson <fjh@cs.mu.oz.au>  |  "I have always known that the pursuit
                                    |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.

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