[Bug c++/71892] Recent optimization changes introduce bugs

["kern at sibbald dot com" <gcc-bugzilla at gcc dot gnu dot org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71892

--- Comment #6 from Kern Sibbald <kern at sibbald dot com> ---
As you say, everything has been said and in any case, it is clear that you are
going to stick with the current compiler behavior. What you have failed to
understand is that I do very well understand that certain things are
"undefined". My complaint is that once you have decided that it is undefined,
the compiler should at print a warning message and then leave the code alone. 
This is what any reasonable compiler would do (IMO). Instead the compiler
disregards what the programmer has written and elides code. I (personally)
classify this this is bad decision making (not conservative) because it made
the "undefined behavior" worse by introducing bugs. Clearly this is my opinion
and not yours, so let's let it drop there because it is your project and your
call.