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

[Robert Lipe <robertlipe at usa dot net>]

About a recent patch, Andreas Jaeger wrote:

> Bootstrapping gcc I get:
> /cvs/gcc/gcc/doloop.c:60: warning: static declaration for `doloop_condition_get' follows non-static

For some compilers, this is a hard error and breaks the build.


I'm not going to fuss about the commit in question.  But in recent
years, a LOT of effort has been spent on getting the warning level in
a full bootstrap down to a manageable number.  (Thanks, Kaveh!)  It's
easy to watch that number decay as code is added back in that isn't held
to the same standards of zero warnings.  Yeah, when major new libraries
come it I can see it taking some time for them to stabilize on all
combinations of builds, but we're consistently seeing defects introduced
into tree that gcc itself would have told us about.

Is it time, in the name of quality/damage control in this project, to
make it an acceptance criteria for any commit that it introduce no new
warnings?

RJL