This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: put setjmp warnings under control of -W
- To: Geoff Keating <geoffk at ozemail dot com dot au>
- Subject: Re: PATCH: put setjmp warnings under control of -W
- From: Marc Lehmann <pcg at opengroup dot org>
- Date: Mon, 1 Nov 1999 03:33:32 +0100
- Cc: Marc Lehmann <pcg at opengroup dot org>, Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, gcc-patches at gcc dot gnu dot org
- References: <19991031221414.A19045@cerebro.laendle> <m3iu3n804w.fsf@gluttony.geoffk.wattle.id.au>
On Mon, Nov 01, 1999 at 12:35:11PM +1100, Geoff Keating <geoffk@ozemail.com.au> wrote:
> > This makes the behaviour consistent with the documentation.
>
> You need to look at the current version of the documentation, which
> says that the warnings are under control of -Wuninitialized.
Hmm... but this change is backwards.. -Wall should never include a warning
that is impossible to work around easily.
> If you really want to have them separate, there is a patch on the
> Cygnus tree which gives them their very own option (this patch has
I donīt want them to have their own switches. I just want the
setjmp/longjmp warnings out of -Wall (which means getting them out of
-Wuninitialized).
> You shouldn't change the behaviour of -Wuninitialized, because there
> are probably people using -Werror -Wno-uninitialized and this would
> break their builds.
I donīt know wether the current behaviour has always been the case (and only
the documentation said something different), but if that is not the case
(setjmp warning under -W), then it cannot break code.
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@opengroup.org |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|