Yep, he's right. i3-2310M is not really a high-end CPU
Thanks for sharing the build! I was gonna compile my own until I found this. Working great so far
Decided to compile my own anyways but Lectrode's guide is way out of date. Do you mind sharing some tips for how you got it to compile? (I saw you posted on his thread too but no solutions).
Edit: nevermind, got it working now. still interested in what optimizations others are using though, i'm testing different ones
Check out the the threads of the (former) ICC compilers
(like me or Lectrode). You'll find useful information about other ICC optimizations
(01-31-2013, 05:47 PM)DefenderX Wrote: [ -> ]Check out the the threads of the (former) ICC compilers (like me or Lectrode). You'll find useful information about other ICC optimizations
I read through all 41 pages of your thread and came to the conclusion that: A: ICC builds offer little difference other than placebo effect, and B: /QaxAVX and /Qopenmp alone seem the best. I tested a lot of /O3 and /Ot but I was getting mixed results. I haven't tested faster floating point models because I'd rather not sacrifice accuracy. I would have to guess most of the bottlenecks in Dolphin are in the JIT/JITIL or the DSP/LLE which we can't really optimize with automagic compiler optimizations. I will still use ICC though because I WANT to believe it's faster
Does anyone know what /Qstd=c++0x /D "nullptr=0" does and why it's needed with ICC builds? Also what is the deal with libiomp5md.dll? my builds run fine with and without this file.
P.S. I can post my 3.5-350 builds in another thread if people want them, but I don't want to piss off the devs since they apparently don't like unofficial builds here.
std=c++0x enables support for c++0x (new c++ standard draft), while nullptr=0 is a definition to compensate for lack of "nullptr" support in ICC compiler (nullptr is a keyword of the new standard, it doesn't really change anything about generated code).
You probably don't need libiomp5.dll because you already have that dll installed system-wide.
(02-01-2013, 04:50 AM)neobrain Wrote: [ -> ]std=c++0x enables support for c++0x (new c++ standard draft), while nullptr=0 is a definition to compensate for lack of "nullptr" support in ICC compiler (nullptr is a keyword of the new standard, it doesn't really change anything about generated code).
You probably don't need libiomp5.dll because you already have that dll installed system-wide.
Thanks, very helpful. I suspected that about libiomp5.dll
Isn't nullptr supported by ICC 13.0? I thought they got it implemented with 12.1 update 6 or something like that, so there would be no need to set it to 0 anymore?
seems to work fine without it, I updated my thread with new builds too but I'm keeping the old ones there too since the new ones have some bugs with alternate wiimote timing removed.
is the /D switch only needed for the nullptr argument?
Can anyone share serious performance test results, this builds vs. master vs. ExtremeDude 2 on a Core I7 SB or IB with OpenMP texture decoder setting enabled? Or in other words, do these builds provide a real measurable speedup like Lectrodes builds did back in the day?