"that UB is apparently explicitly (or maybe implicitly) recognized" Potential UB is identified, but that's absolutely not the same as identifying certain or ev

"that UB is apparently explicitly (or maybe implicitly) recognized" Potential UB is identified, but that's absolutely not the same as identifying certain or even likely UB. For the cases where it's certain or likely as determinable by the compiler: Yes, please turn these into errors and warnings. As I've said, "I would agree it should not be taken as "you should do anything"". But that's as little as I address certain UB, the majority of my post then talks about potential UB in general. I want the optimizer to have free reign to let "anything" happen, by ignoring scenarios which would cause UB, if those scenarios are sufficiently unlikely. Even if that means occasionally backfiring as "unexpected stupid stuff" when statistics catch up to me. I suspect I have a higher tolerance for weirdness in the name of performance than the topic article's author. The majority of my post (including what you quote) then centers on justifying this higher tolerance.