On Mon, 28 Sep 2015, SF Markus Elfring wrote: > >> How do you think about the reuse of the parameter "--recursive-includes" here? > > > > Last time I have tried it, kernel source check took more than 10 hours, > > so I gave up. > > This is interesting background information. > > There are opportunities for more fine-tuning of such a source code analysis, > aren't there? I guess parallelism would be helpful? You could try the following options: -j n --chunksize 10 --recursive-includes --include-headers-for-types where n is the number of cores that you want to use. Parsed header files will be cached within chunks. I don't really know what is the best chunksize. julia > > Regards, > Markus > _______________________________________________ > Cocci mailing list > Cocci@xxxxxxxxxxxxxxx > https://systeme.lip6.fr/mailman/listinfo/cocci > -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
