One thing that -openmp does is cause all local variables to be "automatic", that is, allocated on the stack. If you have any variables that are not initialized, they will have "random" values when you run the program. Make sure all your variables are initialized.

Various problems could be incurred by using a serial pseudo-random number generator in a threaded parallel region. If you keep your random number generator in serial regions and observe precautions which Steve mentioned, you have a reasonable chance of reproducing the previous results.

There are two issues relating to your code and multi-threaded programming:

1) If all threads are using the same pseudo RNG (same sequence of numbers in same pecking order by arbitrary pecking by arbitrary threads), then the "next RNG" must be coded thread-safe. Typically this is by way of a critical section or possibly a CAS / DCAS type of operation. Failure to do so will either messup the sequence or result in multiple threads observing the same RNG at the (approximate) same time.

2) Considering 1 above, while the sequencing of the (thread safe) RNG will be the same, the individual threads pecking order will be non-determinstic. IOW each run may produce different sequences as observed by individal threads.

To correct for this (assuming this is your desire), partition the problem domain into work units for each thread, sequentially generate the random numbers per partiton (i.e. build table of random numbers for each partition), then run the code in parallel with each thread drawing on their own pre-produced random numbers.

Jim Dempsey