...
This compliant solution is explicit in which fields it modifies.:
| Code Block | ||||
|---|---|---|---|---|
| ||||
struct bf {
unsigned int m1 : 8;
unsigned int m2 : 8;
unsigned int m3 : 8;
unsigned int m4 : 8;
}; /* 32 bits total */
void function() {
struct bf data;
data.m1 = 0;
data.m2 = 0;
data.m3 = 0;
data.m4 = 0;
data.m1++;
}
|
...
This compliant solution is explicit in which fields it modifies.:
| Code Block | ||||
|---|---|---|---|---|
| ||||
struct bf {
unsigned int m1 : 6;
unsigned int m2 : 4;
};
void function() {
struct bf data;
data.m1 = 0;
data.m2 = 0;
data.m2 += 1;
}
|
...
Tool | Version | Checker | Description | ||||||
|---|---|---|---|---|---|---|---|---|---|
Compass/ROSE |
|
| Can detect violations of this recommendation. Specifically, it reports violations if
| ||||||
| 94 S | Fully implemented. | |||||||
| PRQA QA-C |
| 0310 | Partially implemented. |
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this recommendation on the CERT website.
...
| CERT C++ Secure Coding Standard | EXP11-CPP. Do not apply operators expecting one type to data of an incompatible type |
| ISO/IEC TR 24772:2013 | Bit Representations [STR] |
| MISRA - C:2012 | Rule 3.5Directive 1.1 (required) |
Bibliography
| [Plum 1985] | Rule 6-5: In portable code, do not depend upon the allocation order of bit-fields within a word |
...