On Wed, Sep 03, 2014 at 08:54:05PM +0200, Thomas Graf wrote: > Make sparse fail and return an error code if a warning is encountered > and -Werror is specified or a hard error is found. This allows to use > sparse in automated build systems to more easily catch new sparse > warnings. > > Due to sparse now returning non zero on failure, the test cases > triggering a error have to be adapated to check for the non zero return > value. > > Also changes cgcc to die if the checker fails. > > Signed-off-by: Thomas Graf <tgraf@xxxxxxx> This seems reasonable. Sparse refrains from showing further warnings after an error, but this turns warnings into errors, so they'll still show up. Not needed for this patch, but would you consider adding -Werror=specific-warning support too? (That'll need some careful thought about the no-warnings-after-error logic, which may or may not make sense.) - Josh Triplett -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
