Suggestion: static code analysis

Suggestion: static code analysis

I'm thinking you perhaps could make a small tool to perform static analysis of a kernel... like some C/C++ tools do ( cppcheck, Visual Studio's static code analysis, etc... ).

The idea is to pass a command line app a folder path ( or a set of files ) so all the .cl archives could be parsed and analyzed. If the app finds, for instance, a buffer overrun then the program could emit via stdout/printf a warning.

You could use this app also to detect performance problems ( for example, suggest for unrolls, detect memory misaligments, etc... )


2 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

As always, great idea!

We like to see such ideas.

I actually think it might be useful add to the Offline
Complier utility already available.


Leave a Comment

Please sign in to add a comment. Not a member? Join today