Hi Josh, On Mon, 2006-11-06 at 10:50 -0800, Josh Triplett wrote: > Regarding your comment about using "make check" for something more useful, I > would greatly welcome a patch which actually checked sparse against all the > files in validation/ and tested what those files intended to test. As far as > I can tell, it looks like some of them may not work as intended right now; for > example, it looks like validation/builtin_safe1.c expects > __attribute__((pure)) and __attribute__((const)) to work and mark a function > as side-effect-free, which doesn't currently happen in sparse. I've just mailed a very primitive testsuite. I would prefer to have a test list and lists for "should be bad" and "known to fail", but it would have to use double loops or some shell tricks (e.g. using environment variables as a hash), so I opted for the simplest approach for now. By the way, I'm not sure how to distinguish sparse errors from sparse warnings short of grepping stderr. For now, any stderr output is an error. -- Regards, Pavel Roskin - 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
