docs/misra: add rule 2.1 exceptions

During the discussions that led to the acceptance of Rule 2.1, we
decided on a few exceptions that were not properly recorded in
rules.rst. Add them now.

Signed-off-by: Stefano Stabellini <stefano.stabellini@amd.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Bertrand Marquis <bertrand.marquis@arm.com>
Release-acked-by: Henry Wang <Henry.Wang@arm.com>
This commit is contained in:
Stefano Stabellini committed 2023-09-29 11:00:47 -07:00
1 parent 0b5bca91aa
commit 5bdfcf7fe8
1 file changed
+10 -1
+10 -1
View File
@@ -107,7 +107,16 @@ maintainers if you want to suggest a change.
* - `Rule 2.1 <https://gitlab.com/MISRA/MISRA-C/MISRA-C-2012/Example-Suite/-/blob/master/R_02_01_1.c>`_
- Required
- A project shall not contain unreachable code
-
- The following are allowed:
- Invariantly constant conditions, e.g. if(IS_ENABLED(CONFIG_HVM)) { S; }
- Switch with a controlling value statically determined not to
match one or more case statements
- Functions that are intended to be referenced only from
assembly code (e.g. 'do_trap_fiq')
- asm-offsets.c, as they are not linked deliberately, because
they are used to generate definitions for asm modules
- Declarations without initializer are safe, as they are not
executed
* - `Rule 2.6 <https://gitlab.com/MISRA/MISRA-C/MISRA-C-2012/Example-Suite/-/blob/master/R_02_06.c>`_
- Advisory
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.