No, I said it had consistent behavior to the compiler. You seem to think I'm saying "undefined behavior means nothing, ignore it"; when what I'm actually sayin

No, I said it had consistent behavior to the compiler. You seem to think I'm saying "undefined behavior means nothing, ignore it"; when what I'm actually saying is "undefined behavior doesn't mean the compiler hasn't defined a behavior and doesn't necessarily = 'bad'". There's dozens of "UB" that C (and C++) developers rely on frequently, because the compilers have defined some behavior they follow; to the point critical portions of the Linux Kernel rely on it (particularly in the form of pointer manipulations). TL;DR - Is UB unsafe to rely on generally? Yes. Should you ignore UB warnings? Definitely not. Does UB mean that the compiler has no idea what to do or is lacking some consistent behavior? Also, no. Know your compiler, and only write code that you know what it does; especially if it's in a murky area like "UB".