What is "a genuine issue that is not a violation" in "3.4 Investigating messages"?

Forum for discussing and asking questions about the MISRA Compliance:2016 "Achieving compliance with MISRA Coding Guidelines"

Moderator: david ward

Post Reply
yohura
Posts: 3
Joined: Mon Apr 22, 2019 12:45 am
Company: B

What is "a genuine issue that is not a violation" in "3.4 Investigating messages"?

Post by yohura » Thu Jul 25, 2019 2:20 am

Hi all,

I'm not sure about "Diagnosis of a genuine issue that is not a violation" in "3.4 Investigating messages".
Are there any example of genuine issue that is not a violation ?

Best regards,

misra-c
Posts: 572
Joined: Thu Jan 05, 2006 1:11 pm

Re: What is "a genuine issue that is not a violation" in "3.4 Investigating messages"?

Post by misra-c » Tue Mar 31, 2020 9:10 am

Toolchains may report a myriad of issues that are not MISRA violations. These could include:
* compile time: eg use of an unsupported language feature
* link time: eg exceeding available memory (RAM or ROM)
---
Posted by and on behalf of
the MISRA C Working Group

Post Reply

Return to “MISRA Compliance discussions”