3 ms·
and clang could any day introduce this behavior if it happened as a consequence of a newly added optimization or something like this. Most "weird" cases like th
by detaro 6y ago
and clang could any day introduce this behavior if it happened as a consequence of a newly added optimization or something like this. Most "weird" cases like this are in the end consequences of optimizations (that people really want and expect of C) combining in a way that causes them. It's not like compiler authors add those issues for fun.
C isn't friendly when it comes to this, UB is dangerous, but given the overall attitude of the ecosystem it's pretty pointless to complain about it.