> The most obscure compiler bug I ever came across was in the Multics BCPL> compiler. It had a code generation bug which depended on which procedure> was done first. It also had a random number generator based on the CPU> clock which determined the order in which code generation was done. So a> correct BCPL program would sometimes compile correctly, and sometimes> incorrectly!>> [Anyone got any insight into why in the world they made a non-deterministic> compiler? -John]

A universal hash function? Guaranteed performance, even in the face of
pathological inputs, because the hash function changes every time and any
given instance of the hash function has a very small chance of being
pathologically bad? Just my guess...

When we self-host, we require our stage-2 and stage-3 object files to differ
only in the time stamps. The occasional uninitialized variable might
generate correct code today but with, e.g., all instances of register 29
and register 17 swapped on different runs. Makes debugging devilishly
difficult.