Page MenuHomePhabricator

Updated 571 Days AgoPublic

The Trusted Firmware follows the MISRA C:2012 coding guidelines. Coverity
Static Analysis is used regularly to generate a report of current defects and
prevent the addition of new ones.

It is not possible for this project to follow all guidelines. The attached
spreadsheet lists all rules and whether the TF aims to comply with them or
not, along with the rationale for each deviation. Note that enforcing a rule
doesn't mean that the codebase is free of defects of that rule, only that
ideally they would be removed.

Note that third-party libraries are not considered in the report (MbedTLS and
libfdt) and we don't intend to fix any defects found in them.

During 2017-2018 there has been an effort to cleanup the codebase of defects,
specially in all code used by BL31 (which is prioritary as it contains all
runtime code). The cleanup has been done mainly in common code and Arm
platforms. No fixes are done to third-party platforms, that is the
responsibility of the maintainers. Further efforts will be done in the future in
the form of general codebase refactoring.

The following graph shows the progress of the MISRA compliance work over the
last year and a half:

Last Author
Last Edited
Feb 26 2019, 1:18 PM

Event Timeline

JoelHutton created this document.Feb 26 2019, 1:17 PM
JoelHutton changed the title from Tf-a-misra-analysis to TF-A-MISRA-Analysis.
JoelHutton edited the content of this document. (Show Details)
JoelHutton edited the content of this document. (Show Details)