Thread safety issue for random_number intrinsic

Reference Number : dpd200111195

Version : Intel Fortran Compiler version 11.0

Operating System : Windows, Linux, Mac OS X

Problem Description :    Calls to the Fortran intrinsic function RANDOM_NUMBER from different threads can sometimes return the same value

Resolution Status :   This has been resolved in the Intel Visual Fortran Compiler for Windows and in the Intel Fortran Compiler for Mac OS X, version 11.1, and in an  update to the Intel Fortran Compiler for Linux, version 11.1. RANDOM_NUMBER generates a single sequence of pseudorandom numbers. Accesses from different threads are synchronized, but the order in which threads access RANDOM_NUMBER, and hence the random_number streams that they receive, may vary from run to run.

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
For more complete information about compiler optimizations, see our Optimization Notice.