#Wine windows 10 emulator mac update

I therefore think that rand() is the culprit. The run time of your program is dominated by the calls to rand().

#Wine windows 10 emulator mac update

The update at the top of the OP's question. Return int(std::floor(rng.frand() * top)) Д®dit: It turned out that the culprit was floor() and not rand() as I suspected - see Int i = next/(1 + (int_max-1)/table_len) Return int(std::floor((std::rand() / (RAND_MAX + 1.0)) * top)) Д¬onst T & operator (int i) const Д¬onst int tmax = 20000 // increase this to make it run longer

The reason I opened a new question on the topic is that now I can post an actual simplified code example for reproducing the phenomenon. Also note that while here I used rand() for simplicity, in the original I used my own RNG which I know does no heap-allocation.

Please see this other question for some more precise benchmarking of the original program (important!!) and the most common possibilities ruled out (such as other programs hogging the CPU on Windows, process startup penalty, difference in system calls such as memory allocation). This particular program does nothing useful, it is just a minimal example boiled down from a larger program I have. The compiled executable is here (if you trust me enough). The source code is at the end of the post. Note that I'm talking about the same executable, not only the same C++ program. The timings are ~15.8 and 25.9 seconds, for Wine and Windows respectively. I have a small C++ program, that, when compiled with nuwen gcc 4.6.1, runs much faster on Wine than Windows XP (on the same computer). This is a followup question to an earlier one: Same program faster on Linux than Windows - why? Solution: Apparently the culprit was the use of floor(), the performance of which turns out to be OS-dependent in glibc.