| |||||||||||||
What every C Programmer should know about undefined behavior #2/3What every C Programmer should know about undefined behavior #2/3Posted May 17, 2011 14:55 UTC (Tue) by nye (guest, #51576)In reply to: What every C Programmer should know about undefined behavior #2/3 by marcH Parent article: What every C Programmer should know about undefined behavior #2/3
>If "dead" is not dead, then there is no problem, correct?
Incorrect - it's not a result of dead code elimination. This bug arises even if dead is used for something later on, because the initial assignment invokes undefined behaviour in the case that P is NULL. It's therefore always conformant for the compiler to assume that P is *not* NULL and remove the check, since if that assumption is incorrect then the behaviour is undefined and the compiler can do whatever it damn well pleases.
(Log in to post comments)
|
|||||||||||||