On 5/17/05, Fredrik Johansson fredrik.johansson@gmail.com wrote:
On 5/17/05, Daniel Wunsch the.gray@gmx.net wrote:
hm.. we all know how badly microbenchmarks can go wrong. in this case i'd have expected the loop to be optimized away, since it does not affect the state of the rest of the program in any way..
What if it's purposefully used to create a delay to avoid a clash between two threads in the control system for a nuclear reactor? ;-)
In that case anyone who uses a waiting loop for a specified number of loops or even a specified time rather than any explicit clash handling, should be fired immediately.
Andre Engels