A recent article by Nick McNamara mentions how static code analysis is useful for embedded software optimization:
"The ESO approach is based around four identifiable and measurable phases: analysis, development, test and maintenance. Firstly, the code base is analysed using any number of tools and techniques to understand worst-case execution time behaviour, or performance of static source-code analysis.
A typical embedded system may contain up to a million lines of source code, or even more. Checking this huge volume of code by hand is clearly not a practical option. Static analysis tries to identify code sequences that might result in buffer overflows, resource leaks, or many other reliability and security problems. Source code analysers do an excellent job at locating a significant class of defects that are not detected by compilers during standard builds and often go undetected during run-time testing or typical field operation. "
Read the complete Reducing costs with embedded software optimization for more on how static code analysis adds value in this context.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment