Re: [Cocci] [PATCH v2] coccinelle: assign signed result to unsigned variable
On Mon, 28 Sep 2015, SF Markus Elfring wrote: > >> Can the Coccinelle software work together with a kind of "precompiled > >> header database"? > > > > There is an option --use-cache, which caches the compiled code > > on the disk. But I have not found the effects to be very satisfactory. > > I am curious if this situation will be improved by further software evolution. There are no plans in that direction. julia -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Cocci] [PATCH v2] coccinelle: assign signed result to unsigned variable
>> Can the Coccinelle software work together with a kind of "precompiled >> header database"? > > There is an option --use-cache, which caches the compiled code > on the disk. But I have not found the effects to be very satisfactory. I am curious if this situation will be improved by further software evolution. Regards, Markus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Cocci] [PATCH v2] coccinelle: assign signed result to unsigned variable
On Mon, 28 Sep 2015, SF Markus Elfring wrote: > > 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. > > Has the make target "coccicheck" direct support for such special parameters? > > > > Parsed header files will be cached within chunks. > > Can the Coccinelle software work together with a kind of "precompiled > header database"? There is an option --use-cache, which caches the compiled code on the disk. But I have not found the effects to be very satisfactory. It is still necessary to read in the serialized code. julia -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Cocci] [PATCH v2] coccinelle: assign signed result to unsigned variable
> 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. Has the make target "coccicheck" direct support for such special parameters? > Parsed header files will be cached within chunks. Can the Coccinelle software work together with a kind of "precompiled header database"? Regards, Markus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Cocci] [PATCH v2] coccinelle: assign signed result to unsigned variable
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 > co...@systeme.lip6.fr > https://systeme.lip6.fr/mailman/listinfo/cocci > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Cocci] [PATCH v2] coccinelle: assign signed result to unsigned variable
On Mon, 28 Sep 2015, SF Markus Elfring wrote: > >> Can the Coccinelle software work together with a kind of "precompiled > >> header database"? > > > > There is an option --use-cache, which caches the compiled code > > on the disk. But I have not found the effects to be very satisfactory. > > I am curious if this situation will be improved by further software evolution. There are no plans in that direction. julia -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Cocci] [PATCH v2] coccinelle: assign signed result to unsigned variable
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 > co...@systeme.lip6.fr > https://systeme.lip6.fr/mailman/listinfo/cocci > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Cocci] [PATCH v2] coccinelle: assign signed result to unsigned variable
> 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. Has the make target "coccicheck" direct support for such special parameters? > Parsed header files will be cached within chunks. Can the Coccinelle software work together with a kind of "precompiled header database"? Regards, Markus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Cocci] [PATCH v2] coccinelle: assign signed result to unsigned variable
On Mon, 28 Sep 2015, SF Markus Elfring wrote: > > 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. > > Has the make target "coccicheck" direct support for such special parameters? > > > > Parsed header files will be cached within chunks. > > Can the Coccinelle software work together with a kind of "precompiled > header database"? There is an option --use-cache, which caches the compiled code on the disk. But I have not found the effects to be very satisfactory. It is still necessary to read in the serialized code. julia -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Cocci] [PATCH v2] coccinelle: assign signed result to unsigned variable
>> Can the Coccinelle software work together with a kind of "precompiled >> header database"? > > There is an option --use-cache, which caches the compiled code > on the disk. But I have not found the effects to be very satisfactory. I am curious if this situation will be improved by further software evolution. Regards, Markus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
