lib/bitmanipulation: Define AoU #2339
Conversation
|
|
|
The created documentation from the pull request is available at: docu-html |
aschemmel-tech
left a comment
aschemmel-tech
left a comment
There was a problem hiding this comment.
see inline comments
| :safety: ASIL_B | ||
| :status: valid | ||
|
|
||
| The user shall ensure that bit positions and bit ranges passed to bit manipulation functions are within valid bounds for the integral type being operated on. Bit positions must not exceed the type's bit width. |
There was a problem hiding this comment.
How can this be read together with comp_req__bitmanipulation__bounds_safety: "if you give the bitmanipulation functions some wrong range then you will have to cope with an error return" or "if you give the bitmanipulation functions some wrong range then you may get back some wrong value" ?
docs/modules/baselibs/bitmanipulation/docs/requirements/index.rst
Outdated
Show resolved
Hide resolved
rahulthakre29
force-pushed
the
AoU_for_bitmanipulation_lib
branch
from
d85f386 to
fca4bfb
Compare
| :status: valid | ||
|
|
||
| The user shall ensure that bit positions and bit ranges passed to bit manipulation functions are within valid bounds for the integral type being operated on. Bit positions must not exceed the type's bit width. | ||
| The bit manipulation API shall validate bit positions and ranges are within the integral type's bit width and prevent data corruption through bounds checking. |
There was a problem hiding this comment.
but after this change it is not a Assumption of Use any more, but a requirement to be fulfilled by bit manipulation. More or less the same as comp_req__bitmanipulation__bounds_safety.
2 participants
Defined AoU for library bitmanipulation