> > Excellent. I would welcome any attempts at cross-function and cross-file > checking, rather than continuing to add annotations for that purpose. I experimented with a patch some time ago that allowed us to run sparse on all files in a directory for the kernel. But I experienced OOM while checking the XFS sources. Reply on the matter from Linus was at that time something in the line of that sparse did not do any atemp to free up memory after the early parse stage so it is consuming much more memory than needed. This was almost one year ago so things may have changed - but at least something to keep an eye on. XFS was just triggering this - it surely was due to codesize alone so any other big directory could have been the trigger too. It is not XFS specific. Sam - 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
