Fixed undefined behavior in RNG.
authorsvenpanne@chromium.org <svenpanne@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 13 Jun 2014 06:36:09 +0000 (06:36 +0000)
committersvenpanne@chromium.org <svenpanne@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 13 Jun 2014 06:36:09 +0000 (06:36 +0000)
commitac18d082505f1dfd17a0e3b937b88e848f36d189
treef1a4ac8fbef4592fb29dbc82cdc85f4edbe1bcaf
parent817430f6cec5f5b386512b22a9df7efcc9d89fa3
Fixed undefined behavior in RNG.

We're basically trading undefined behavior for implementation defined
behavior, which should be OK for UBSan. :-) The generated code should
be identical, at least I checked that for GCC 4.6.3 on x64.

BUG=377790
LOG=y
R=dcarney@chromium.org

Review URL: https://codereview.chromium.org/332733002

git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21828 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/utils/random-number-generator.cc