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 d

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.