3 ms·
> It's not on by default but is effectively on in any codebase where anyone cares... Then why is this a MISRA rule by itself? Shouldn't it just be "every codeb
by n144q 2y ago
> It's not on by default but is effectively on in any codebase where anyone cares...
Then why is this a MISRA rule by itself? Shouldn't it just be "every codebase must compile with -Wall or equivalent"?
- jpc0 2y agoI wouldn't be surprised if you could justify in a review the compiling with -Wall (probably more explicitly) catches this and therefore you can disregard the rule. Not all compilers have a -Wall equivalent, GCC, Clang and MSVC does but RANDOM_EMBEDDED_CHIP's custom compiler might not and that is a valid target for MISRA compliance. I doubt every single thing that needs MISRA get's compiled with an industry standard compiler, I wouldn't be surprised that GCC is the exception for most companies targeting MISRA compliance.