On 04/03/2015 13:17, Magnus Ihse Bursie wrote:
:
I intend to file individual bugs to handle these remaining warnings,
so the net result will be a completely warning free build.
I also intend to file individual bugs on all the libraries that has
had warnings disabled. I expect the outcome of these bugs to be either:
A) The code modified so it does not trigger warnings, and the warnings
re-enabled, or
B) The warnings (or a subset of them) kept disabled, but a comment
added to the makefile describing why this is the proper course of action.
Not all bugs might be worth fixing. For instance, the GCC warnings
type-limits, sign-compare, pointer-to-int-cast, conversion-null,
deprecated-declarations, clobbered, int-to-pointer-cast and
type-limits are all more or less benign, and is possibly the result of
a false positive.
Right, although for some of these it is important to double check.
Do you plan to paste in the warnings into the bugs that you will create?
That wold be useful as warnings are a moving target.
-Alan
