Dolphin, the GameCube and Wii emulator - Forums

After I finally managed to compile it with the Intel XE Compiler 2013.1.119 I thought I would share my build. It is optimized for AVX with some other optimizations (which I don't really know much about to be honest).

new build Dolphin 3.5-397 x64 AVX optimized compiled with the Intel XE Compiler 2013.2.149
http://www12.zippyshare.com/v/53416078/file.html

older builds:

Dolphin 3.5-395 x64 AVX optimized compiled with the Intel XE Compiler 2013.2.149
http://www16.zippyshare.com/v/72268008/file.html

Dolphin 3.5-382 x64 AVX optimized compiled with the Intel XE Compiler 2013.2.149
http://www8.zippyshare.com/v/76838472/file.html

Dolphin 3.5-392 x64 AVX optimized compiled with the Intel XE Compiler 2013.2.149
http://www49.zippyshare.com/v/64102647/file.html

Dolphin 3.5-375 x64 AVX optimized compiled with the Intel XE Compiler 2013.2.149
http://www72.zippyshare.com/v/9513066/file.html

Dolphin 3.5-368 x64 AVX optimized compiled with the Intel XE Compiler 2013.2.149
http://www49.zippyshare.com/v/64477357/file.html

Which scene on Melee or Brawl?

You forget to distribute the libiomp5md.dll with the download. If you compile, you have two options to link the libraries: dynamically and statically.
Dynamically will require the .dll installed on the hosts pc, while statically will "embed" the libraries in the application itself. Both have pro's and con's.

(01-24-2013, 11:54 PM)Garteal Wrote: [ -> ]You forget to distribute the libiomp5md.dll with the download. If you compile, you have two options to link the libraries: dynamically and statically.
Dynamically will require the .dll installed on the hosts pc, while statically will "embed" the libraries in the application itself. Both have pro's and con's.

I'd like to hear them if you don't mind

hmm there was no libiomp5md.dll after the compile.. Or do I have to add the lib myself or something like that? And the scene was just a saved single player level on Brawl which had some major slowdowns. I know that this is not really a good or objective comparison between builds, but it took me almost a whole week to get it compiled at all (had this xilink error which I mentioned in a different thread since last Thursday..). So I was just happy to get it finally done . It is the single player stage with pit against Peach, Samus and cpt falcon. It's just something I noticed in my first minutes of playing with the new build. The non ICC Build was 3.5-320 btw. so it can be an improvement from that too.

EDIT: I found the file in many Intel folders like "C:\Program Files (x86)\Intel\Composer XE\redist\intel64\compiler", should I just copy the file into the Dolphin root folder if I upload my builds?

Yup
Its no longer possible to static link to libiomp5 unfortunately.
@Edude
Off the top of my head dynamic linking gives you a smaller exe though if you distribute the dll's anyway its a loss since static linking will only include the functions used and dll's can be updated e.g. when MS patches the C runtime. Static linking can be faster, avoids dll hell and obviously the dll missing altogether.

Marking unofficial.

tested it but had many slowdowns.

for some reason the 3.0-413 AVX INTEL x64 OPENMP O3 revision still the fastest for me

I noticed they also removed lot of options like lock threads to cores at the dolphin 3.5 version D:

I think I will stick with my previous version for now.

(01-27-2013, 12:51 PM)kasar Wrote: [ -> ]I noticed they also removed lot of options like lock threads to cores at the dolphin 3.5 version D:

No they didn't, that was removed after

after?

do you mean in this specific relase?

also dont know why that option got removed, I think it is a must have for people with HT proccesors , it also allow to see when dolphin is CPU limited.

for example,I think mine is bottlenecked emulating the GPU thread, getting very little VFPS sometimes.

OCing my i3 laptop improved things a little, but still not enough to get constant full speed from most demanding Gamecube games like metroid games.

An i3 isn't a high-end processor, it's likely your bottleneck