Jump to content

Xorshift: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Removed reference to KISS ([17,13,5] not being a triplet for a proper xorshift implementation, and misleading), rectified claims to be closer to reality (re cryptography and BigCrush)
m Removed loaded language
Line 3: Line 3:
Xorshift generators are among the fastest non-cryptographic random number generators requiring minimal code and state. Although they do not pass every statistical test without further refinement, this weakness is well-known and easily amended (as pointed out by Marsaglia in the original paper) by combining them with a non-linear function, resulting e.g. in a xorshift+ or xorshift* generator. A naive C implementation of a xorshift+ generator that passes all tests from the BigCrush suite (with an order of magnitude fewer failures than MT or WELL) typically takes fewer than 10 clock cycles on x86 to generate a random number thanks to instruction pipelining.<ref name="shootout"/>
Xorshift generators are among the fastest non-cryptographic random number generators requiring minimal code and state. Although they do not pass every statistical test without further refinement, this weakness is well-known and easily amended (as pointed out by Marsaglia in the original paper) by combining them with a non-linear function, resulting e.g. in a xorshift+ or xorshift* generator. A naive C implementation of a xorshift+ generator that passes all tests from the BigCrush suite (with an order of magnitude fewer failures than MT or WELL) typically takes fewer than 10 clock cycles on x86 to generate a random number thanks to instruction pipelining.<ref name="shootout"/>


Because plain xorshift generators (without non-linear step) fail a few statistical tests, they have been accused of being unreliable<ref>http://www.iro.umontreal.ca/~lecuyer/myftp/papers/xorshift.pdf See 8. Conclusion</ref> and not suitable for [[cryptography|cryptographic purposes]]. However, considering the previous paragraph, it is highly debatable whether this is a fair objection or whether the authors even bothered to read the original papers carefully.
Because plain xorshift generators (without non-linear step) fail a few statistical tests, they have been accused of being unreliable<ref>http://www.iro.umontreal.ca/~lecuyer/myftp/papers/xorshift.pdf See 8. Conclusion</ref> and not suitable for [[cryptography|cryptographic purposes]]. However, considering the previous paragraph, it is debatable whether or not this is a fair objection.


==Example implementation==
==Example implementation==

Revision as of 15:09, 3 July 2014

Xorshift random number generators form a class of pseudorandom number generators that were discovered by George Marsaglia.[1] They generate the next number in their sequence by repeatedly taking the exclusive or of a number with a bit shifted version of itself. This makes them extremely fast on modern computer architectures. The xor shift primitive is invertible if the number of combinations is odd, but not otherwise [2](most textbook xorshift implementations have 3 combinations, since this is the minimum number for a maximum period generator, given correct parameters). They are a subclass of linear feedback shift registers, but their simple implementation typically makes them faster and use less space.[3] However, the parameters have to be chosen very carefully in order to achieve a long period.[4]

Xorshift generators are among the fastest non-cryptographic random number generators requiring minimal code and state. Although they do not pass every statistical test without further refinement, this weakness is well-known and easily amended (as pointed out by Marsaglia in the original paper) by combining them with a non-linear function, resulting e.g. in a xorshift+ or xorshift* generator. A naive C implementation of a xorshift+ generator that passes all tests from the BigCrush suite (with an order of magnitude fewer failures than MT or WELL) typically takes fewer than 10 clock cycles on x86 to generate a random number thanks to instruction pipelining.[5]

Because plain xorshift generators (without non-linear step) fail a few statistical tests, they have been accused of being unreliable[6] and not suitable for cryptographic purposes. However, considering the previous paragraph, it is debatable whether or not this is a fair objection.

Example implementation

A C version[note 1] of one xorshift algorithm [1] is:

#include <stdint.h>

/* These state variables must be initialized so that they are not all zero. */

uint32_t x, y, z, w;

uint32_t xor128(void) {
    uint32_t t;

    t = x ^ (x << 11);
    x = y; y = z; z = w;
    return w = w ^ (w >> 19) ^ t ^ (t >> 8);
}

This algorithm has a maximal period of 2128 − 1[4] and passes the diehard tests. However, it fails the MatrixRank and LinearComp tests of the BigCrush test suite from the TestU01 framework.

Variations

All xorshift generators fail some test out of TestU01's BigCrush test suite (this is true of all generators based on linear recurrences such as the Mersenne Twister or WELL). However, it is easy to scramble the output of such generators to improve their quality.

A xorshift* generator applies a multiplication to the output of a xorshift generator, as suggested by Marsaglia. The following 64-bit generator with 64 bits of state has a maximal period of 264 − 1[7] and fails only the MatrixRank test of BigCrush:

#include <stdint.h>

uint64_t x; /* The state must be seeded with a nonzero value. */

uint64_t next(void) {
	x ^= x >> 12; // a
	x ^= x << 25; // b
	x ^= x >> 27; // c
	return x * 2685821657736338717LL;
}

A similar generator is suggested in Numerical Recipes,[8] but it fails also the BirthdaySpacings test.

The following generator, instead, has 1024 bits of state, a maximal period of 21024 − 1[7] and passes BigCrush:

#include <stdint.h>

/* The state must be seeded so that it is not everywhere zero. If you have
   a 64-bit seed,  we suggest to seed a xorshift64* generator and use its
   output to fill s. */

uint64_t s[ 16 ]; 
int p;

uint64_t next(void) { 
	uint64_t s0 = s[ p ];
	uint64_t s1 = s[ p = ( p + 1 ) & 15 ];
	s1 ^= s1 << 31; // a
	s1 ^= s1 >> 11; // b
	s0 ^= s0 >> 30; // c
	return ( s[ p ] = s0 ^ s1 ) * 1181783497276652981LL; 
}

Both generators, as all xorshift* generators of maximal period, emit a sequence of 64-bit values that is equidistributed in the maximum possible dimension.[7]

The following xorshift+ generator, instead, has 128 bits of state, a maximal period of 2128 − 1[9] and passes BigCrush:

#include <stdint.h>

/* The state must be seeded so that it is not everywhere zero. */

uint64_t s[ 2 ];

uint64_t next(void) { 
	uint64_t s1 = s[ 0 ];
	const uint64_t s0 = s[ 1 ];
	s[ 0 ] = s0;
	s1 ^= s1 << 23;
	return ( s[ 1 ] = ( s1 ^ s0 ^ ( s1 >> 17 ) ^ ( s0 >> 26 ) ) ) + s0;
}

This generator is one of the fastest generator passing BigCrush;[5] however, it is only 1-dimensionally equidistributed.[9] It is a variation of the XSadd generator,[10] which however fails several BigCrush tests when reversed.

Uses

WebKit's JavaScript Core (and hence Apple's Safari browser) uses the Xorshift RNG to supply random numbers for Math.random() in client JavaScript.[11]

Notes

  1. ^ In C, the caret (^) represents the bitwise XOR, and " << " the bit shift.

References

  1. ^ a b Marsaglia, George (July 2003). "Xorshift RNGs". Journal of Statistical Software. 8 (14).
  2. ^ Attention: This template ({{cite doi}}) is deprecated. To cite the publication identified by doi:10.1080/00207161003596708, please use {{cite journal}} (if it was published in a bona fide academic journal, otherwise {{cite report}} with |doi=10.1080/00207161003596708 instead.
  3. ^ Brent, Richard P. (August 2004). "Note on Marsaglia's Xorshift Random Number Generators". Journal of Statistical Software. 11 (5).
  4. ^ a b Panneton, François (October 2005). "On the xorshift random number generators" (PDF). ACM Transactions on Modeling and Computer Simulation (TOMACS). 15 (4).
  5. ^ a b "xorshift*/xorshift+ generators and the PRNG shootout".
  6. ^ http://www.iro.umontreal.ca/~lecuyer/myftp/papers/xorshift.pdf See 8. Conclusion
  7. ^ a b c Vigna, Sebastiano (2014). "An experimental exploration of Marsaglia's xorshift generators, scrambled". arXiv:1402.6246.
  8. ^ Press, WH; Teukolsky, SA; Vetterling, WT; Flannery, BP (2007). "Section 7.1.2.A. 64-bit Xorshift Method". Numerical Recipes: The Art of Scientific Computing (3rd ed.). New York: Cambridge University Press. ISBN 978-0-521-88068-8.{{cite book}}: CS1 maint: postscript (link)
  9. ^ a b Vigna, Sebastiano (2014). "Further scramblings of Marsaglia's xorshift generators". arXiv:1404.0390.
  10. ^ "XSadd".
  11. ^ Bortz, Andrew (7 March 2013). "Bug 111533 - Replace Mersenne Twister RNG with a simple but fast RNG". WebKit. Retrieved 2 January 2014.