From: Bob Jamison <rjamison@ti...> - 2005-03-15 15:30:36
I spent a few hours yesterday compiling the tree
with gcc4.0.0, and removing the warnings, so it
should compile fairly cleanly now.
Since warnings are a useful tool to indicate possible
bugs (and I found one yesterday), can people please
make sure that their committed code compiles without
them? I know that "unused variable" and things like
that can be a pain to avoid, especially in a "work in
But if we allow ourselves to become desensitized to warnings,
we will likely ignore problem conditions and possible bugs.
From: Peter Moulder <Peter.M<oulder@in...> - 2005-03-15 23:48:05
On Tue, Mar 15, 2005 at 09:30:30AM -0600, Bob Jamison wrote:
> I spent a few hours yesterday compiling the tree
> with gcc4.0.0, and removing the warnings, so it
> should compile fairly cleanly now.
> Since warnings are a useful tool to indicate possible
> bugs (and I found one yesterday), can people please
> make sure that their committed code compiles without
I agree with this. Even if the warning for your code doesn't indicate
a bug, the warning makes it harder for other people to notice warnings
introduced by their code, and more work to step through warnings &
errors in one's editor.
(If you compile in a terminal rather than from your editor, then use
`make -s' to prevent most output other than warnings so that warnings
stand out. Directing stdout to /dev/null goes further still, while
still showing warnings & errors.)