This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
-Wuninitialized vs. docs vs. setjmp/longjmp
- To: gcc-bugs at gcc dot gnu dot org
- Subject: -Wuninitialized vs. docs vs. setjmp/longjmp
- From: Marc Lehmann <pcg at opengroup dot org>
- Date: Tue, 26 Oct 1999 04:30:20 +0200
I just got gobs of
"warning: variable `d2' might be clobbered by `longjmp' or `vfork'"
messages with -Wall (in fact, -Wunitialized). The documentation clearly
says that this is _only_ done when I specify -W.
The documented way makes more sense, since uninitialized variable warnings
can easily be avoided, while longjmp clobberings can not.
If you agree I'll send a patch to seperate the warnings in
uninitialized_vars_warning and setjmp_args_warning from -Wuninitialized.
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@opengroup.org |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|