MISRA C makes SW "robust" against compiler failures

[dg1980]

This could get interesting - i assume that is the same like tool qualification in ISO 26262 (e.g. https://www.jnovel.co.jp/en/service/comp...26262.html)?

Anyways, i personally divide MISRA rules in three big categories:

• Purely about code style (e.g. writing 1U instead 1u, using unique identifiers, etc.)
  
• Purely about avoiding implementation defined behavior (e.g. size of an integer)
  
• Purely about avoiding undefined behavior (e.g. casting away const)

While the last two items greatly increase portability and safety of the code they do not protect you in any way from a buggy optimizer in your compiler which in turn messes up your binary (after all, a compiler is just another piece of software and software has bugs).
So, based on my experience i would answer your question about robustness against compiler failures with no, but i am very much interested in other people's opinions on this subject.