There's bigger issue than stuffing. In "rural" Hungary chain voting is customary where people are taken to the voting place by gangs and are either awarded with some money or a bag of potatoes, or threatened to be beaten if they do not comply. The first voter of the chain goes in, takes the ballot, hides it and takes it out. It is then pre-filled by the gang. The next voters take the prefilled ballot in, throw it in the box and bring a fresh clean ballot out, and so on...
In other cases, people get money/bag of potatoes for a photo of their correctly filled ballot.
* Do this with "<0" and ">=0" to only test the sign of the result. A
* good compiler would generate better code (and a really good compiler
* wouldn't care). Gcc is currently neither.
It's funny the love-hate relationship the Linux kernel has with GCC. It's the only supported compiler[1], and yet...
[1] can Clang fully compile Linux yet? I haven't followed the updates in a while.
To be fair this comment predates git history (before 2005) when GCC wasn't a very good compiler. The kernel developers at one point were sticking with a specific version of GCC because later versions would miscompile the kernel. Clang didn't exist then.
Do I understand it correctly that the logic is that if timestamp B is above timestamp A, but the difference is more than half of the unsigned range, B is considered to happen before A?
Yes. When the timestamps wrap it's fundamentally ambiguous, but this will be correct unless the timestamps are very far apart (and the failure mode is more benign: a really long time difference being considered shorter is better than all time differences being considered zero after the timestamp wraps).
reply