* Jeff Law: >> I think the open issues are: >> * Do we want to implement something else beside implicit-int and >> implicit-function-declaration? (Candidates are int-conversion and >> incompatible-pointer-types, and the void vs non-void part of >> return-type, maybe others as previously discussed on the list.) >> * How do we divide up the test suite cleanup work?
> Not to open a can of worms, but shouldn't these be evaluated along the > same basic criteria? ie, what's Clang doing here, are these > warnings-as-errors and thus apply to system headers, etc. ANd the > biggie, do any of these issues tend to mask correctness errors in the > wild at a level roughly similar to implicit > int/implicit-function-declaration? At present, it is not possible to evaluate them using the same basic criteria because we don't have the answer to your last question. I have an instrumented compiler for -Wint-conversion, but have not had a chance yet to run a distribution rebuild with it. Thanks, Florian
