MISRA C Rule 17.7 states: "The value returned by a function having non-void return type shall be used."
Deviate functions like 'memcpy()', 'memset()', 'memmove()', as they return a value purely for convenience, their primary functionality (memory manipulation) remains unaffected, and their return values are generally non-critical and seldom relied upon. Update 'deviations.rst' file accordingly. No functional changes. Signed-off-by: Dmytro Prokopchuk <dmytro_prokopch...@epam.com> --- Changes in v2: - removed snprintf(), strlcpy(), strlcat() from the patch scope Test CI pipeline: https://gitlab.com/xen-project/people/dimaprkp4k/xen/-/pipelines/2003537146 Link to v1: https://patchew.org/Xen/ad15582787e675fadf92502f85041c3232749a99.1756112701.git.dmytro._5fprokopch...@epam.com/ --- automation/eclair_analysis/ECLAIR/deviations.ecl | 5 +++++ docs/misra/deviations.rst | 7 +++++++ 2 files changed, 12 insertions(+) diff --git a/automation/eclair_analysis/ECLAIR/deviations.ecl b/automation/eclair_analysis/ECLAIR/deviations.ecl index 7f3fd35a33..8335af1bce 100644 --- a/automation/eclair_analysis/ECLAIR/deviations.ecl +++ b/automation/eclair_analysis/ECLAIR/deviations.ecl @@ -575,6 +575,11 @@ safe." -config=MC3A2.R17.7,calls+={safe, "any()", "decl(name(__builtin_memcpy||__builtin_memmove||__builtin_memset||cpumask_check))"} -doc_end +-doc_begin="It is safe to deviate functions like 'memcpy()', 'memset()', 'memmove()', as they return a value purely for convenience, +their primary functionality (memory manipulation) remains unaffected, and their return values are generally non-critical and seldom relied upon." +-config=MC3A2.R17.7,calls+={safe, "any()", "decl(name(memcpy||memset||memmove))"} +-doc_end + # # Series 18. # diff --git a/docs/misra/deviations.rst b/docs/misra/deviations.rst index 2119066531..5ee97f41e8 100644 --- a/docs/misra/deviations.rst +++ b/docs/misra/deviations.rst @@ -576,6 +576,13 @@ Deviations related to MISRA C:2012 Rules: - __builtin_memset() - cpumask_check() + * - R17.7 + - It is safe to deviate functions like 'memcpy()', 'memset()', 'memmove()', + as they return a value purely for convenience, their primary functionality + (memory manipulation) remains unaffected, and their return values are + generally non-critical and seldom relied upon. + - Tagged as `safe` for ECLAIR. + * - R18.2 - Subtractions between pointers where at least one of the operand is a pointer to a symbol defined by the linker are safe. -- 2.43.0
