Yes. And that would make sense. They might not insist on exactly this, but they already leave this sort of possibility open by suggesting that undefined behavi

Yes. And that would make sense. They might not insist on exactly this, but they already leave this sort of possibility open by suggesting that undefined behaviour could result in the program behaving "in a documented manner characteristic of the environment". If the standard writers' hands were tied by having to cater for every system they'd ever heard of, even the stupid ones where shifting by 32 (or whatever) results in rand() (or whatever) - implementers' hands are not! They have only one system to think about! If that system happens to be one of the stupid ones - well, anybody working on it will have exactly the same problem. But if it isn't one of the stupid ones - why do they insist that their users should behave as if it is?