MISRA C:2012 - Best Practices and Tools for Writing High-Quality C Code
Misra C 2012 Pdf Downloadl
If you are a software developer who works with embedded systems, you may have heard of Misra C. It is a set of guidelines for writing safe, reliable, and portable code in the C programming language. But what exactly is Misra C and why is it important? In this article, we will explore the history, benefits, features, challenges, and future of Misra C, focusing on the latest version, Misra C 2012. We will also show you how to download a pdf copy of the standard for your reference.
Misra C 2012 Pdf Downloadl
The History of Misra C
Misra C stands for Motor Industry Software Reliability Association C. It was originally developed by a consortium of automotive companies in the UK in 1998, as a way to improve the quality and safety of software used in vehicles. The first version of Misra C contained 127 rules that were derived from the ISO standard for C (ISO/IEC 9899:1990).
Since then, Misra C has been revised and updated several times to reflect the changes in the C language and the needs of the industry. The second version, Misra C 2004, added more rules and clarified some ambiguities. The third version, Misra C 2012, was released in March 2013, with significant enhancements and additions. It is currently the most widely used and accepted version of Misra C.
The Benefits of Misra C
Misra C is designed to help developers write code that is safe, reliable, and portable. By following the rules and guidelines of Misra C, developers can avoid common errors and pitfalls that may lead to bugs, crashes, vulnerabilities, or undefined behavior. Some of the benefits of using Misra C are:
Safety: Misra C helps prevent errors that may cause harm to people or property, such as buffer overflows, memory leaks, division by zero, or pointer arithmetic. This is especially important for software that is used in safety-critical systems, such as automotive, aerospace, medical, or industrial applications.
Reliability: Misra C helps ensure that the software behaves consistently and predictably, regardless of the input or environment. It also helps detect and handle errors gracefully, without causing system failures or data corruption.
Portability: Misra C helps make the software independent of the hardware platform, compiler, or operating system. It also helps avoid features or constructs that may not be supported or may behave differently on different platforms.
The Features of Misra C 2012
Misra C 2012 is based on the ISO standard for C (ISO/IEC 9899:1999), also known as C99. It contains 143 rules and 16 directives that cover various aspects of the language, such as syntax, semantics, data types, operators, expressions, control structures, functions, pointers, arrays, strings, preprocessor directives, and library functions. The rules and directives are classified into three categories:
Mandatory: These are the rules and directives that must be followed in all cases. Violating a mandatory rule or directive may result in a fatal error or undefined behavior.
Required: These are the rules and directives that should be followed in all cases, unless there is a strong justification for deviation. Violating a required rule or directive may result in a serious error or undesirable behavior.
Advisory: These are the rules and directives that should be followed where possible, but may be deviated from if there is a good reason. Violating an advisory rule or directive may result in a minor error or suboptimal behavior.
Some of the main changes and additions in Misra C 2012 are:
Compliance Levels
Misra C 2012 introduces the concept of compliance levels to allow developers to choose the level of rigor and strictness they want to apply to their code. There are three compliance levels:
Fully compliant: This means that the code follows all the mandatory, required, and advisory rules and directives of Misra C 2012.
Required compliant: This means that the code follows all the mandatory and required rules and directives of Misra C 2012.
Mandatory compliant: This means that the code follows all the mandatory rules and directives of Misra C 2012.
Deviations and Justifications
Misra C 2012 recognizes that there may be situations where developers need to deviate from some of the rules or directives for valid reasons. For example, they may need to use a non-compliant feature for performance optimization, compatibility with legacy code, or interoperability with external systems. In such cases, developers can document their deviations and justifications using a standardized format and process. This helps ensure that the deviations are intentional, controlled, and traceable.
Directives and Decidable Rules
Misra C 2012 distinguishes between rules and directives. Rules are statements that can be checked by a tool or a human reviewer. Directives are statements that require human judgment or interpretation. For example, Rule 1.1 states that "The implementation shall be compliant with ISO/IEC 9899:1990". This can be checked by a tool or a human reviewer. Directive 4.1 states that "Run-time failures shall be minimized". This requires human judgment or interpretation.
Misra C 2012 also distinguishes between decidable and undecidable rules. Decidable rules are rules that can be checked by a tool without any false positives or false negatives. Undecidable rules are rules that cannot be checked by a tool without any false positives or false negatives. For example, Rule 8.1 states that "Types shall be explicitly specified". This is a decidable rule that can be checked by a tool without any false positives or false negatives. Rule 8.13 states that "A pointer should point to a const-qualified type whenever possible". This is an undecidable rule that cannot be checked by a tool without any false positives or false negatives.
Static Analysis Tools
The Challenges of Misra C 2012
While Misra C 2012 offers many benefits, it also poses some challenges and limitations for developers. Some of the difficulties and drawbacks of using Misra C 2012 are:
Compatibility Issues
Misra C 2012 may cause compatibility problems with other standards and libraries that are not compliant with it. For example, some of the rules and directives of Misra C 2012 may conflict with the rules and directives of other coding standards, such as CERT C, ISO/IEC TS 17961, or MISRA C++. Similarly, some of the features or functions of Misra C 2012 may not be supported or may behave differently by some compilers, platforms, or operating systems. This may require developers to use conditional compilation, wrappers, or adapters to ensure compatibility.
Performance Overheads
Misra C 2012 may affect the performance and efficiency of the software in some cases. For example, some of the rules and directives of Misra C 2012 may restrict the use of optimization techniques, such as inline functions, macros, or bit fields. Similarly, some of the features or functions of Misra C 2012 may introduce additional overheads, such as runtime checks, assertions, or logging. This may require developers to balance the trade-offs between safety and performance.
Learning Curve
Misra C 2012 may require developers to learn and master a large number of rules and directives that cover various aspects of the language. This may take time and effort, especially for developers who are new to Misra C or who are used to different coding styles or practices. Moreover, developers may need to keep up with the updates and revisions of Misra C 2012 as they are released. This may require developers to invest in training, documentation, or tools to support their learning and compliance.
The Future of Misra C 2012
Misra C 2012 is not a static standard that remains unchanged over time. It is a dynamic standard that evolves and adapts to the changes in the technology and industry. Some of the trends and developments that may influence the future of Misra C 2012 are:
New Technologies and Platforms
New technologies and platforms may affect the applicability and relevance of Misra C 2012 in different ways. For example, new technologies and platforms may introduce new features or functions that are not covered by Misra C 2012 or that may violate some of its rules or directives. This may require developers to extend or modify Misra C 2012 to accommodate them. Alternatively, new technologies and platforms may offer better alternatives or solutions than Misra C 2012 for achieving safety, reliability, and portability. This may reduce the need or demand for Misra C 2012.
New Standards and Guidelines
New standards and guidelines may complement or compete with Misra C 2012 in different ways. For example, new standards and guidelines may provide more specific or comprehensive guidance for certain domains or applications that are not adequately addressed by Misra C 2012. This may increase the value or usefulness of Misra C 2012 by integrating it with them. Conversely, new standards and guidelines may provide more general or flexible guidance for various domains or applications that are already covered by Misra C 2012. This may decrease the value or usefulness of Misra C 2012 by replacing it with them.
Conclusion
Misra C 2012 is a set of guidelines for writing safe, reliable, and portable code in the C programming language. It is based on the ISO standard for C (ISO/IEC 9899:1999) and contains 143 rules and 16 directives that cover various aspects of the language. It also introduces the concept of compliance levels, deviations and justifications, directives and decidable rules, and static analysis tools to help developers comply with the standard.
Misra C 2012 offers many benefits for developers who work with embedded systems or safety-critical systems. It helps prevent errors and pitfalls that may cause harm to people or property, ensure consistent and predictable behavior of the software regardless of the input or environment, and make the software independent of the hardware platform, compiler, or operating system.
However, Misra C 2012 also poses some challenges and limitations for developers. It may cause compatibility problems with other standards and libraries that are not compliant with it, affect the performance and efficiency of the software in some cases, and require a steep learning curve to master the rules and directives of the standard.
Misra C 2012 is not a final or fixed standard that remains unchanged over time. It is a dynamic and evolving standard that adapts to the changes in the technology and industry. It may be influenced by new technologies and platforms that introduce new features or functions or offer better alternatives or solutions, and by new standards and guidelines that provide more specific or comprehensive guidance or more general or flexible guidance.
If you are interested in learning more about Misra C 2012 or downloading a pdf copy of the standard, you can visit the official website of Misra at https://www.misra.org.uk/.
FAQs
Here are some frequently asked questions about Misra C 2012:
Q: What is the difference between Misra C and Misra C++?
A: Misra C++ is a separate set of guidelines for writing safe, reliable, and portable code in the C++ programming language. It is based on the ISO standard for C++ (ISO/IEC 14882:2003) and contains 228 rules that cover various aspects of the language. It is not compatible with Misra C, as C++ is a superset of C with many additional features and functions.
Q: How can I check if my code is compliant with Misra C 2012?
A: You can use static analysis tools to check if your code is compliant with Misra C 2012. Static analysis tools are software tools that analyze the source code without executing it. They can detect errors, bugs, vulnerabilities, violations, or deviations from the rules and directives of Misra C 2012. Some examples of static analysis tools that support Misra C 2012 are PC-lint, LDRA Testbed, PRQA QA-C, Parasoft C/C++test, and IAR Embedded Workbench.
Q: How can I learn more about Misra C 2012?
A: You can learn more about Misra C 2012 by reading the official document of the standard, which is available for purchase from the Misra website at https://www.misra.org.uk/Publications/tabid/57/Default.aspx. You can also read books, articles, blogs, or tutorials that explain the rules and directives of Misra C 2012 in detail. Some examples are "MISRA-C:2004 - Guidelines for the use of the C language in critical systems" by MISRA Consortium, "MISRA-C:2012 - An introduction" by David Ward, "MISRA-C:2012 - Guidelines for the use of the C language in critical systems" by MISRA Consortium, and "MISRA-C:2012 - A brief overview" by Elektrobit.
Q: How can I download a pdf copy of Misra C 2012?
A: You can download a pdf copy of Misra C 2012 by purchasing it from the Misra website at https://www.misra.org.uk/Publications/tabid/57/Default.aspx. The pdf copy costs 15.00 (excluding VAT) for a single user license. You can also download a free sample of Misra C 2012 from the same website.
71b2f0854b