This is the mail archive of the
mailing list for the GCC project.
Re: "introduce no new bootstrap warning" criteria. was: Loop iv debugging patch
- To: aj at suse dot de, robertlipe at usa dot net
- Subject: Re: "introduce no new bootstrap warning" criteria. was: Loop iv debugging patch
- From: dewar at gnat dot com
- Date: Fri, 12 Jan 2001 10:21:30 -0500 (EST)
- Cc: gcc at gcc dot gnu dot org
<<I don't think we can demand absolutly no new warnings. But we could
classify the warnings and demand that some warnings (like the one I
reported and fixed) are forbidden but others are ok
(e.g. signed/unsigned compares).
I prefer a zero warnings criterion for the bootstrap, but for that you
definitely need the feature to selectively turn off warnings for a
particular section of code.
In GNAT, we have a compiler option to make all warnings fatal, and we
always use this option for all builds. We have also adopted a zero
warnings tolerance for all our C code.
Obviously this cannot happen over night, but I think it is a very
useful goal. There is something about zero warnings that is considerably
more useful than "few" warnings.