News for hackers. Stuff that matters.

A comment on Undefined behavior is often a thing for C programmers (2011). Parent comment

Re:Undefined behavior is often a thing for C programmers (2011) by abainbridge on Thursday September 03, 2020 @11:57AM (#24365322)
No. Letting the hardware just do its thing. Like an out of bounds memory access or divide by zero.

Editing here because it looks like we've hit the max reply depth. This wouldn't be like UB in the same way that code that could generate an out-of-bounds memory accesses is not UB. The critical thing is that the compiler should assume that the hardware error does not occur.

[ Parent | on HN ]
Re:Undefined behavior is often a thing for C programmers (2011) by chrisseaton on Thursday September 03, 2020 @11:59AM (#24365356)
But how would that be different to UB? If you let the hardware do whatever it wants that's no different to UB doing whatever it wants.
[ Parent | on HN ]