This is the mail archive of the 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

* Joseph S. Myers ( [20010112 15:15]:

> What happened to the idea of a pragma to mark particular warnings as
> expected in code - whether globally, scoped with push/pop, or for a
> particular line of code only?

Well, it got discussed and then none had time (or interest?) to actually
implement it. Now that we have _Pragma in, there is nothing really blocking
implementation of '#pragma GCC waring ...', that is besides of volunteers to
actually do it ;-)

> With the preferred design from previous
> discussions being, I think, a regular expression describing the expected
> English language warning text,

Well, my favourite is still much easier to implement. I'd simply use the
name of a warning to specify it. Thus you'd do something like this:

#pragma GCC warning push
#pragma GCC warning unused off
<some code>
#pragma GCC warning pop.

What we might need for this to get really usefull would be to make warnings
more fine grained.


Philipp Thomas <>
Development, SuSE GmbH, Schanzaecker Str. 10, D-90443 Nuremberg, Germany

Penguins shall save the dinosaurs
                          -- Handelsblatt about Linux on S/390

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