What is "a genuine issue that is not a violation" in "3.4 Investigating messages"? - Printable Version +- MISRA Discussion Forums (https://forum.misra.org.uk) +-- Forum: MISRA Compliance (https://forum.misra.org.uk/forumdisplay.php?fid=23) +--- Forum: MISRA Compliance discussions (https://forum.misra.org.uk/forumdisplay.php?fid=184) +--- Thread: What is "a genuine issue that is not a violation" in "3.4 Investigating messages"? (/showthread.php?tid=1499) |
What is "a genuine issue that is not a violation" in "3.4 Investigating messages"? - yohura - 25-07-2019 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, Re: What is "a genuine issue that is not a violation" in "3.4 Investigating messages"? - misra-c - 31-03-2020 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) |