The deterministic random number generation function does not produce values on the full 32-bit signed possible range about octane

[GoogleCodeExporter]

What this basically means is that we produce only 28 random bits, with your 
change it would be 31, with 
https://code.google.com/p/v8/source/browse/branches/bleeding_edge/src/math.js#18
0 it would be 32. Of course the RNG will still not produce most numbers in 
[0..1), because the IEEE 754 mantissa has 52 bits, while we produce 32. So 
changing this will make things marginally better, but I think it's not worth 
the trouble for the benchmark suite. Furthermore, any change here would mean 
that we would not be able to compare benchmark numbers before and after this 
change anymore, which would be unfortunate.

If somebody fundamentally disagrees, feel free to re-open this issue, but 
otherwise I think we won't take any action here.

Original comment by [email protected] on 16 Apr 2014 at 11:03

• Changed state: WontFix