> So it was decided to make oversized shifts UB. Exactly the stupidity I was pointing out - why make it undefined behaviour, when you could make it implementat

> So it was decided to make oversized shifts UB. Exactly the stupidity I was pointing out - why make it undefined behaviour, when you could make it implementation-defined behaviour. You might argue the effects are the same, but they aren't, of course - the first is global (the whole program is invalid), whereas the second is local (only that instruction has an unknown (but probably still deterministic) outcome, and only in specific circumstances).