Hi DenisDenis P. Mendoza wrote:Thanks, I'm just new to this stuff and I'm no "guru". I only developed much of this through constant practice and from "Matser Jim' himselfDavid Dahlem wrote:Hi DenisDenis P. Mendoza wrote:Hello David,David Dahlem wrote:I downloaded the 30 day trial of the new Intel C++ Compiler version 10.1.020 available here ...
https://registrationcenter.intel.com/Re ... ister.aspx
It's supposed to support the IDE integration of VS2008, but doesn't seem to work with my 2008 express version. So i'm trying to learn how to use the Intel compiler on the command line. I admit i am almost a complete dummy with compilers, and especially the command line.
I have managed to compile a simple Hello.cpp file on the Intel command line with this command - icl Hello.cpp. Could someone help a compiler idiot with the commands for multiple source files?
Thanks
Dave
Welcome to the Intel compiling group. I've been an IDE dependent before, but later on found out that compiling in command prompt is much easier.
Here's a simple tip:
1. Let's say we want to compile Fruit 2.1 src. Extract it in a folder location like c:\fruit21src
2. Start your IA-32 32-bit compiler in command prompt. Type "cd" then click space, and type the location of source, which is "c:\fruit21src". Press enter and your 'source" location will display at command prompt.
3. For ease in typing the command lines, you could prepare the long scripts in a text editor like notepad. Here's the following sample:
(or add some "spices" like /Qunroll /fp:fast /Zp16 (experiment with them))Code: Select all
icl -o fruit.exe *.cpp /nologo /MT /W3 /DWIN32 /DNDEBUG /D_CONSOLE /D_MBCS /G7 /Ox /QxK /Qipo /Qprof-gen
Copy and paste it at command prompt, then press "enter".
4. Run some games/epd tests without closing "console", using the "instrumented" engine - fruit.exe. Collect enough profiling data - .dyn files.
5. After profiling, compile your optimized code using the same flags. just replace /Qprof-gen with /Qprof-use. You'll now have Fruit.exe with PGO.
For ease again, here is your last command lines:
Copy and paste it at command prompt, then press "enter".Code: Select all
icl -o fruit.exe *.cpp /nologo /MT /W3 /DWIN32 /DNDEBUG /D_CONSOLE /D_MBCS /G7 /Ox /QxK /Qipo /Qprof-use
I hope this helps David.
Denis
Wow, tips from a great compiling guru!! Thank you, this should help me a lot. I'll try your tips. My time is limited, i may be moving to a new home next week, and i want to get a fast build of Sage to release before i move.
Thanks
Dave. I only share what I learned from him. And yes, it is much easier to make a bat file for this pupose - no sweat
. You'll forget about your IDE as time goes on.
We'll be waiting for yoiur Intel optimized "Super Sage"!
[/code]
I've forgotten my IDE already.

I've learned to do PGO compiling on the Intel command line now!! It's awesome, create much faster builds. But it's slow and tiresome, the way i have to do it. There must be a way to automate this process. In order to create the .dyn files, i manually entered 25 epd positions and let Sage analyze for 10 seconds.
Can this be automated somehow with a .bat file? And another question, will the amount of .dyn files created make a difference, will more be better?
Anyway, thanks for the great tips. I'll probably release a new version of Sage soon.
Regards
Dave